From: Nicholas Piggin <npiggin@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/64: BE option to use ELFv2 ABI for big endian kernels
Date: Sat, 07 Mar 2020 10:58:54 +1000 [thread overview]
Message-ID: <1583542596.l37hgse8mc.astroid@bobo.none> (raw)
In-Reply-To: <20200305105503.GZ22482@gate.crashing.org>
Segher Boessenkool's on March 5, 2020 8:55 pm:
> On Thu, Mar 05, 2020 at 01:34:22PM +1000, Nicholas Piggin wrote:
>> Segher Boessenkool's on March 4, 2020 9:09 am:
>> >> +override flavour := linux-ppc64v2
>> >
>> > That isn't a good name, heh. This isn't "v2" of anything... Spell out
>> > the name "ELFv2"? Or as "elfv2"? It is just a name after all, it is
>> > version 1 in all three version fields in the ELF headers!
>>
>> Yeah okay. This part is only for some weird little perl asm generator
>> script, but probably better to be careful. linux-ppc64-elfv2 ?
>
> That generator is from openssl, or inspired by it, it is everywhere.
> So it is more important to get it right than it would seem at first
> glance ;-)
>
> That name looks perfect to me. You'll have to update REs expecting the
> arch at the end (like /le$/), but you had to already I think?
le$ is still okay for testing ppc64le, unless you wanted me to add the
-elfv2 suffix on there as well? If that was the case, for consistency
we'd also have to add -elfv1 for the BE v1 case. I was just going to add
-elfv2 for the new variant.
Thanks,
Nick
next prev parent reply other threads:[~2020-03-07 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 1:45 [PATCH] powerpc/64: BE option to use ELFv2 ABI for big endian kernels Nicholas Piggin
2020-03-03 23:09 ` Segher Boessenkool
2020-03-05 3:34 ` Nicholas Piggin
2020-03-05 10:55 ` Segher Boessenkool
2020-03-07 0:58 ` Nicholas Piggin [this message]
2020-03-09 21:48 ` 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=1583542596.l37hgse8mc.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).