From: Michael Ellerman <mpe@ellerman.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>,
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: Tue, 04 May 2021 22:15:34 +1000 [thread overview]
Message-ID: <875yzyae55.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20210503151824.GJ10366@gate.crashing.org>
Segher Boessenkool <segher@kernel.crashing.org> writes:
> On Mon, May 03, 2021 at 10:51:41AM +1000, Nicholas Piggin wrote:
>> Excerpts from Segher Boessenkool's message of May 3, 2021 3:55 am:
>> > 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.
>>
>> Then I'm not sure what the point of your previous mail was, what did I
>> miss?
>
> I asked if you could make it clearer to people who do not know what this
> is whether they want to use it. Or that was my intention, anyhow :-/
>
>> > 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 :-)
>>
>> The point was for people who don't know ELFv2 has a specific meaning for
>> powerpc,
>
> It does not have *any* meaning outside of Power. But people who do not
> know what it is can assume the wrong things about it. It isn't a great
> name because of that :-(
>
> (It's not as bad as the MIPS ABIs -- an older one is called "new" :-) )
>
>> then ELF ABIv2 is more explanatory about it being an abi change
>> rather than base elf change, even if it's not the "correct" name.
>
> I very much disagree. "ELF ABIv2" is completely meaningless.
Except:
$ readelf -h /bin/true
ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: PowerPC64
Version: 0x1
Entry point address: 0x1990
Start of program headers: 64 (bytes into file)
Start of section headers: 66176 (bytes into file)
Flags: 0x2, abiv2
^^^^^
:)
cheers
next prev parent reply other threads:[~2021-05-04 12:16 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
2021-05-03 0:51 ` Nicholas Piggin
2021-05-03 15:18 ` Segher Boessenkool
2021-05-04 12:15 ` Michael Ellerman [this message]
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=875yzyae55.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=segher@kernel.crashing.org \
/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.