From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v2] powerpc/64: BE option to use ELFv2 ABI for big endian kernels
Date: Wed, 5 May 2021 07:31:11 -0500 [thread overview]
Message-ID: <20210505123111.GN10366@gate.crashing.org> (raw)
In-Reply-To: <875yzyae55.fsf@mpe.ellerman.id.au>
On Tue, May 04, 2021 at 10:15:34PM +1000, Michael Ellerman wrote:
> Segher Boessenkool <segher@kernel.crashing.org> writes:
> > On Mon, May 03, 2021 at 10:51:41AM +1000, Nicholas Piggin wrote:
> >> 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
> ^^^^^
Ha :-)
This can also print "abiv1" or even "abiv0", btw:
case EM_PPC64:
if (e_flags & EF_PPC64_ABI)
{
char abi[] = ", abiv0";
abi[6] += e_flags & EF_PPC64_ABI;
strcat (buf, abi);
}
break;
This is only in readelf, and the main audience for readelf is the people
who know all details about what means what already. But, do you have a
suggestion for better output here?
Segher
next prev parent reply other threads:[~2021-05-05 12:34 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
2021-05-05 12:31 ` Segher Boessenkool [this message]
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=20210505123111.GN10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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 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).