From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Nicholas Piggin <npiggin@gmail.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 0/4] powerpc/64: ELFv2 conversion
Date: Fri, 05 May 2023 22:21:15 +1000 [thread overview]
Message-ID: <87wn1n55qc.fsf@mail.lhotse> (raw)
In-Reply-To: <6d0609ae-e31b-8530-7509-7861b07d66c7@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 05/05/2023 à 09:18, Nicholas Piggin a écrit :
>> This series has the steps to remove ELFv1 from the kernel build.
>> Patch 1 is a build fix, 2 defaults everything to ELFv2, 3 is
>> really a separate issue that concerns userspace. 4 removes v1
>> support.
>
> I see CONFIG_MPROFILE_KERNEL is restricted to LITTLE_ENDIAN. Is that
> correct ? Don't we have mprofile_kernel as well on BIG ENDIAN once
> switched to ABI v2 ? If so, can we drop the -pg based profiling
> completely, or is CLANG still not supporting mprofile_kernel ?
Clang does not support -mprofile-kernel.
AIUI they would like us to switch to -fpatchable-function-entry which
could then be supported on GCC & clang.
That would be a nice cleanup but also a bunch of work that no one has
found time to do.
https://github.com/linuxppc/issues/issues/447
https://github.com/llvm/llvm-project/issues/57031
So for now we need to keep the -pg based version.
cheers
next prev parent reply other threads:[~2023-05-05 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 7:18 [PATCH 0/4] powerpc/64: ELFv2 conversion Nicholas Piggin
2023-05-05 7:18 ` [PATCH 1/4] powerpc/64: Force ELFv2 when building with LLVM linker Nicholas Piggin
2023-05-05 21:39 ` Nathan Chancellor
2023-05-05 21:39 ` Nathan Chancellor
2023-05-05 7:18 ` [PATCH 2/4] powerpc/64: Make ELFv2 the default for big-endian builds Nicholas Piggin
2023-05-05 7:18 ` [PATCH 3/4] powerpc/64s: Remove support for ELFv1 little endian userspace Nicholas Piggin
2023-05-05 7:18 ` [RFC PATCH 4/4] powerpc/64: Remove support for kernel's built with ELFv1 ABI Nicholas Piggin
2023-05-05 8:49 ` Christophe Leroy
2023-05-09 8:25 ` Nicholas Piggin
2023-05-05 8:51 ` [PATCH 0/4] powerpc/64: ELFv2 conversion Christophe Leroy
2023-05-05 12:21 ` Michael Ellerman [this message]
2023-05-05 15:08 ` Naveen N. Rao
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=87wn1n55qc.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--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.