From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/64: BE option to use ELFv2 ABI for big endian kernels
Date: Sun, 2 May 2021 12:55:06 -0500 [thread overview]
Message-ID: <20210502175506.GE10366@gate.crashing.org> (raw)
In-Reply-To: <1588121596.7zej1imag0.astroid@bobo.none>
On Wed, Apr 29, 2020 at 10:57:16AM +1000, Nicholas Piggin wrote:
> Excerpts from Segher Boessenkool's message of April 29, 2020 9:40 am:
> I blame toolchain for -mabi=elfv2 ! And also some blame on ABI document
> which is called ELF V2 ABI rather than ELF ABI V2 which would have been
> unambiguous.
At least ELFv2 ABI is correct. "ELF ABI v2" is not.
> I can go through and change all my stuff and config options to ELF_ABI_v2.
Please don't. It is wrong. Both the original PowerPC ELF ABI and the
ELFv2 one have versions themselves. Also, the base ELF standard has a
version, and is set up so there can be incompatible versions even! Of
course it still is version 1 to this day, but :-)
Segher
next prev parent reply other threads:[~2021-05-02 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 11:25 [PATCH v2] powerpc/64: BE option to use ELFv2 ABI for big endian kernels Nicholas Piggin
2020-04-28 23:40 ` Segher Boessenkool
2020-04-29 0:57 ` Nicholas Piggin
2021-05-02 17:55 ` Segher Boessenkool [this message]
2021-05-03 0:51 ` Nicholas Piggin
2021-05-03 15:18 ` Segher Boessenkool
2021-05-04 12:15 ` Michael Ellerman
2021-05-05 12:31 ` Segher Boessenkool
2021-05-02 16:57 ` Michal Suchánek
2021-05-03 0:58 ` Nicholas Piggin
2021-05-03 7:11 ` Michal Suchánek
2021-05-03 9:34 ` Michal Suchánek
2021-05-03 20:17 ` Michal Suchánek
2021-05-04 9:13 ` Nicholas Piggin
2021-05-04 17:41 ` Naveen N. Rao
2021-05-04 18:08 ` Michal Suchánek
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=20210502175506.GE10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@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.