From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: "Oliver O'Halloran" <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Nicholas Piggin <npiggin@gmail.com>,
Alan Modra <amodra@gmail.com>
Subject: Re: [RFC][PATCH] powerpc/64be: use ELFv2 ABI for big endian kernels
Date: Thu, 24 Nov 2016 17:17:16 -0600 [thread overview]
Message-ID: <20161124231716.GB30675@gate.crashing.org> (raw)
In-Reply-To: <87d1hktt5z.fsf@concordia.ellerman.id.au>
On Fri, Nov 25, 2016 at 09:22:16AM +1100, Michael Ellerman wrote:
> >> >> Question, are there any fundamental reasons we shouldn't use the ELFv2
> >> >> ABI to build big endian kernels if the compiler supports it?
> >> >
> >> > No one uses ELFv2 for BE in production, and it isn't thoroughly tested
> >> > at all, not even regularly tested. "Not supported", as far as GCC is
> >> > concerned (or any of the distros AFAIK).
> >>
> >> Is this actually unsupported by gcc?
> >
> > It may or may not work. We of course try to keep it working, or make
> > it work if it doesn't now. But it isn't regularly tested, and it isn't
> > a target that is considered for the release criteria (see
> > https://gcc.gnu.org/gcc-7/criteria.html -- powerpc64{,le}-linux, i.e.
> > ABIv1 for BE, ABIv2 for LE).
>
> It doesn't actually say that though. It just says
> powerpc64-unknown-linux-gnu. So how is someone, say the musl folks,
> supposed to know that BE ABIv2 is not supported?
Because their target is powerpc64*-*-linux-musl instead? It is not on
the release criteria list, it is not something we make any claims about.
How would you know -m32 -mlittle is not well tested at all? It is in much
the same boat: unusual combinations of options, and unusual configurations,
are not well tested. You have to build a separate C library just to get
started with it, that should tell you there are some rough waters ahead!
Which isn't to say you should not do this -- just think twice before
doing so. And wear a life vest.
Segher
next prev parent reply other threads:[~2016-11-24 23:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 13:08 [RFC][PATCH] powerpc/64be: use ELFv2 ABI for big endian kernels Nicholas Piggin
2016-11-23 14:20 ` Balbir Singh
2016-11-23 14:38 ` Segher Boessenkool
2016-11-24 4:42 ` Nicholas Piggin
2016-11-24 5:37 ` Oliver O'Halloran
2016-11-24 12:27 ` Segher Boessenkool
2016-11-24 22:22 ` Michael Ellerman
2016-11-24 23:17 ` Segher Boessenkool [this message]
2016-11-25 1:13 ` Nicholas Piggin
2016-11-25 2:08 ` Michael Ellerman
2016-11-25 2:35 ` Nicholas Piggin
2016-11-25 3:35 ` Michael Ellerman
2016-11-25 2:02 ` Michael Ellerman
2016-11-25 14:59 ` Segher Boessenkool
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=20161124231716.GB30675@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=amodra@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oohall@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.