[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200604174613.GP1079@brightrain.aerifal.cx>
Date: Thu, 4 Jun 2020 13:46:13 -0400
From: Rich Felker <dalias@...c.org>
To: Segher Boessenkool <segher@...nel.crashing.org>
Cc: Daniel Kolesa <daniel@...aforge.org>,
Michal Suchánek <msuchanek@...e.de>,
Joseph Myers <joseph@...esourcery.com>, libc-alpha@...rceware.org,
eery@...erfox.es, musl@...ts.openwall.com,
Will Springer <skirmisher@...tonmail.com>,
Palmer Dabbelt via binutils <binutils@...rceware.org>,
via libc-dev <libc-dev@...ts.llvm.org>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: Re: ppc64le and 32-bit LE userland compatibility
On Thu, Jun 04, 2020 at 12:33:12PM -0500, Segher Boessenkool wrote:
> On Thu, Jun 04, 2020 at 01:18:44PM -0400, Rich Felker wrote:
> > On Thu, Jun 04, 2020 at 12:12:32PM -0500, Segher Boessenkool wrote:
> > > On Tue, Jun 02, 2020 at 05:13:25PM +0200, Daniel Kolesa wrote:
> > > > well, ppc64le already cannot be run on those, as far as I know (I
> > > > don't think it's possible to build ppc64le userland without VSX in
> > > > any configuration)
> > >
> > > VSX is required by the ELFv2 ABI:
> > >
> > > """
> > > Specifically, to use this ABI and ABI-compliant programs, OpenPOWER-
> > > compliant processors must implement the following categories:
> >
> > This is not actually ABI but IBM policy laundered into an ABI
> > document, which musl does not honor.
>
> It is the ABI. If you think it should be different, make your own ABI,
> don't pretend the existing ABI is different than what it is. Thank you.
Our ABI is as specified in the ELFv2 document, but with ld as ld64,
and minus gratuitous requirements on ISA level that are not part of
implementing linkage.
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.
