From: David Edelsohn <dje.gcc@gmail.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: Re: musl libc for PPC64
Date: Mon, 8 Feb 2016 12:48:48 -0500 [thread overview]
Message-ID: <CAGWvnymnYg_tE0mrUKN7JMuLb29D_BfqJMOL12MXRui5-C0_xw@mail.gmail.com> (raw)
In-Reply-To: <20160208165143.GA9349@brightrain.aerifal.cx>
On Mon, Feb 8, 2016 at 11:51 AM, Rich Felker <dalias@libc.org> wrote:
> On Mon, Feb 08, 2016 at 05:17:58PM +0100, Szabolcs Nagy wrote:
>> * David Edelsohn <dje.gcc@gmail.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
next prev parent reply other threads:[~2016-02-08 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 14:43 David Edelsohn
2016-02-08 16:17 ` Szabolcs Nagy
2016-02-08 16:51 ` Rich Felker
2016-02-08 17:48 ` David Edelsohn [this message]
2016-02-08 20:18 ` Rich Felker
2016-02-08 20:30 ` David Edelsohn
2016-02-08 22:59 ` Rich Felker
2016-02-08 23:24 ` David Edelsohn
2016-02-08 23:29 ` Rich Felker
2016-02-08 23:48 ` Szabolcs Nagy
2016-02-09 1:03 ` Szabolcs Nagy
2016-02-09 1:16 ` David Edelsohn
2016-02-09 1:42 ` Szabolcs Nagy
2016-02-09 1:45 ` Szabolcs Nagy
2016-02-09 1:52 ` Rich Felker
2016-02-09 2:06 ` David Edelsohn
2016-02-10 22:17 ` David Edelsohn
2016-02-08 23:52 ` David Edelsohn
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=CAGWvnymnYg_tE0mrUKN7JMuLb29D_BfqJMOL12MXRui5-C0_xw@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=dalias@libc.org \
--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).