From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: musl 0.9.8 released
Date: Wed, 28 Nov 2012 08:05:07 -0500 [thread overview]
Message-ID: <20121128130507.GP20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <20121127205116.1dbf130f.idunham@lavabit.com>
On Tue, Nov 27, 2012 at 08:51:16PM -0800, Isaac Dunham wrote:
> > > -planned subarches: mipsel32-sf, mips32-sf
> >
> > My idea for the names would be something like: mips, mipsel, mips-sf,
> > mipsel-sf, ...
>
> > Basically, the full arch name would be something along the lines of:
> >
> > arch[el|eb][-abivariant]
> >
> > which could be represented as $(ARCH)$(ENDIAN)$(ABIVARIANT), where
> > only $(ARCH)$(ABIVARIANT) and $(ARCH) should be needed to search for
> > asm files. But additional considerations need to be made for how the
> > main arch dir with bits headers and internal headers would be
> > selected. I don't think we want to duplicate entire arch trees for
> > subarchs, but I also don't see how subarchs can get by with using the
> > same set of headers unless we rely on the compiler to predefine macros
> > that distinguish them. This is rather ugly but we're already partially
> > relying on it for endianness varants.
>
> Where would the headers need to differ by subarch?
> I'm guessing this is mainly stuff like fenv?
Yes, probably the floating-point headers are the main places: fenv.h,
float.h, and math.h.
> > > -unsupported subarches: i386
> >
> > ??
> The 80386 processor, as opposed to 80486.
>
> # On x86, make sure we don't have incompatible instruction set
> # extensions enabled by default. This is bad for making static binaries.
> # We cheat and use i486 rather than i386 because i386 really does not
> # work anyway (issues with atomic ops).
This is fairly comparable to the mips1 issue and the need for ll/sc
emulation by the kernel. i386 is just fundamentally lacking in a way
that makes multi-tasking/multi-threading not workable with the POSIX
apis for it. The kernel should be emulating 'lock cmpxchg', like it
does ll/sc for mips1, and if it did, 386 would work fine. But
apparently nobody cares anyway..
> Also, I can't seem to find it now, but somewhere I heard that
> upstream gcc and/or glibc with the "i386-linux-*" triplet has some
> incompatability with "i486-linux-*". IIRC, I heard that some distros
> patch this to treat i386-linux-* as if it meant i486.
> But, I can't trace the source for that claim, so don't count on it...
This doesn't make any sense to me.
> > > It seems Debian's using aarch64-* for ARMv8.
> >
> > Yes, 64-bit arm is a new arch and it seems they used the name aarch64
> > instead of arm64 due to arm* being interpreted as 32-bit arm by many
> > things..
> >
> ie, due to the insane number of ABIs and triplets that ARM has?
> arm (bigendian/OABI), armeabi (bigendian: armeb), armel
> (littleendian variant of EABI), armhf (armel + vfp3)
:-)
Rich
next prev parent reply other threads:[~2012-11-28 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 2:49 Rich Felker
2012-11-27 11:31 ` Szabolcs Nagy
2012-11-27 14:46 ` Rich Felker
2012-11-28 2:43 ` Isaac Dunham
2012-11-28 3:39 ` Rich Felker
2012-11-28 4:51 ` Isaac Dunham
2012-11-28 13:05 ` Rich Felker [this message]
2012-11-28 21:35 ` Rob Landley
2012-11-28 23:53 ` Rich Felker
2012-11-29 0:52 ` Rob Landley
2012-12-03 13:11 ` Szabolcs Nagy
2012-12-03 17:30 ` Rich Felker
2012-12-03 22:03 ` Szabolcs Nagy
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=20121128130507.GP20323@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/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).