mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Tom Storey <tom@snnap.net>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Building for m68k
Date: Wed, 22 Apr 2020 22:32:55 -0400	[thread overview]
Message-ID: <20200423023255.GO11469@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAFDgZgUw_KybjBsYm_+i0xSMWrajYz65DtaN=fjTTbN+sBfKsQ@mail.gmail.com>

On Thu, Apr 23, 2020 at 12:05:27PM +1000, Tom Storey wrote:
> Hi all.
> 
> Is anyone out there particularly familiar with building musl for the m68k?
> 
> I was able to successfully build it, but then later discovered that it
> would appear to be targeting 68020+ processors more specifically. I would
> like to build for the earlier 680[01]0's.
> 
> Specific examples are to do with (at least) aio where some atomic
> instructions are used (e.g. cas - compare and swap) which only exist for
> the 68020 and later, but not for earlier processors.
> 
> https://git.musl-libc.org/cgit/musl/tree/src/aio/aio.c#n375
> https://git.musl-libc.org/cgit/musl/tree/arch/m68k/atomic_arch.h
> 
> Thus, adding -m68000 to the CFLAGS env variable when trying to do a rebuild
> results in a failure complaining that the 68020+ is required. I dont know
> what else is hiding away in the rest of it that will also be
> incompatible... :-)
> 
> Any suggestions, pointers, tips would be greatly appreciated.

To answer this I think we need to know how Linux support for these
models is meant to work (if it even is meant to). If Linux does
trap-and-emulate (I'm not aware of any other mechanism it has by which
it could make this work) then it might just amount to passing the
right -Wa,... to make the assembler accept instructions not supported
in the target ISA level. But it could mean there are missing
prerequisites that have to be fixed on the kernel side before anything
can actually work.

Rich

  reply	other threads:[~2020-04-23  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23  2:05 Tom Storey
2020-04-23  2:32 ` Rich Felker [this message]
2020-04-23  5:04   ` Tom Storey
2020-04-23 16:30     ` Rich Felker
2020-04-24  0:36       ` Tom Storey
2020-04-24  0:51         ` Rich Felker
2020-04-24  1:14           ` Tom Storey
2020-04-24  1:20             ` Rich Felker
2020-04-24  2:29               ` Tom Storey
2020-04-24  2:37                 ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200423023255.GO11469@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=tom@snnap.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).