[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGWvnymnYg_tE0mrUKN7JMuLb29D_BfqJMOL12MXRui5-C0_xw@mail.gmail.com>
Date: Mon, 8 Feb 2016 12:48:48 -0500
From: David Edelsohn <dje.gcc@...il.com>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: Re: musl libc for PPC64
On Mon, Feb 8, 2016 at 11:51 AM, Rich Felker <dalias@...c.org> wrote:
> On Mon, Feb 08, 2016 at 05:17:58PM +0100, Szabolcs Nagy wrote:
>> * David Edelsohn <dje.gcc@...il.com> [2016-02-08 09:43:08 -0500]:
>> > What work is necessary to enable basic musl libc support for PPC64
>> > Linux Little Endian?
>>
>> once the abi is clear (is long double ieee128?) the arch specific
>> parts of musl need to be ported for ARCH=powerpc64.
>
> IIRC one of the powerpc64 ABIs uses function descriptors rather than
> normal function pointers. If so that may affect a few details in the
> dynamic linker and may require some changes to non-arch-specific code,
> but since we have SH/FDPIC all the basic framework for function
> descriptors should be there already.
PPC64LE Linux is little endian and does not use function descriptors.
> Also to clarify what you asked about long double ABI, if ieee128
> (quad) is not used, the compiler needs to be built to use plain double
> (ieee64 double) for long double instead of using ibm double-double.
GCC can use IEEE64 or IEEE128 for long double.
Is there any internal interest from the musl libc community for PPC64
support that IBM could sponsor with a financial bounty on
bountysource.com?
Thanks, David
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.
