[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191214181712.GX1666@brightrain.aerifal.cx>
Date: Sat, 14 Dec 2019 13:17:12 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: max_align_t mess on i386
On Sat, Dec 14, 2019 at 06:51:50PM +0100, Florian Weimer wrote:
> * Rich Felker:
>
> > However, whatever we do with i386, the option of using 8-byte
> > granularity remains open for all the other 32-bit archs, most of which
> > tend to be used with machines far more memory-constrained than i386.
>
> Note that powerpc has a similar issue, but with long double:
>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=6527>
>
> But perhaps musl follows the old powerpc ABI, where double and long
> double are both binary64 (I have not checked, sorry).
We use the ld64 powerpc ABI. musl doesn't support non-IEEE-semantics
floating point types (stuff like IBM double-double) and quad was not
an option at the time, and if it's even supported now it's messy and
requires very recent tooling.
BTW I know someone from our community doing both musl and glibc stuff
on powerpc is actually interested in continuing to use the ld64 ABI
(with the old compat symbols) on glibc due to problems with
double-double support in applications.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
