From: Torsten Duwe <duwe@lst.de>
To: Anton Blanchard <anton@samba.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
live-patching@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: -mprofile-kernel vs. notrace in ppc64(le) Linux kernels
Date: Sun, 27 Sep 2015 13:06:33 +0200 [thread overview]
Message-ID: <20150927110633.GA9572@lst.de> (raw)
In-Reply-To: <20150927090348.3c725ab4@kryten>
On Sun, Sep 27, 2015 at 09:03:48AM +1000, Anton Blanchard wrote:
> > On Sat, Sep 26, 2015 at 04:30:08PM +0200, Torsten Duwe wrote:
> > > kernel. It is mapped to GCC's (4.8, FWIW)
> > > __attribute__((no_instrument_function)), which, to my surprise,
> > > works for -p and -pg nicely, but does not affect -mprofile-kernel
> > > at all!
>
> This sounds like the issue below, fixed by Pat.
>
> diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
> index 289b52c..a479219 100644
> --- a/gcc/config/rs6000/rs6000.c
> +++ b/gcc/config/rs6000/rs6000.c
> @@ -23198,7 +23198,7 @@ rs6000_output_function_prologue (FILE *file,
> /* Output -mprofile-kernel code. This needs to be done here instead of
> in output_function_profile since it must go after the ELFv2 ABI
> local entry point. */
> - if (TARGET_PROFILE_KERNEL)
> + if (TARGET_PROFILE_KERNEL && crtl->profile)
> {
> gcc_assert (DEFAULT_ABI == ABI_AIX || DEFAULT_ABI == ABI_ELFv2);
> gcc_assert (!TARGET_32BIT);
Yes, indeed!
I can see the fix in the 4.9 branch, it's in 5.x and 6.x, but _not_ in 4.8.5 :(
That's what you get when you use "stable" distributions.
Thanks a lot for the pointer!
Torsten
next prev parent reply other threads:[~2015-09-27 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 14:30 -mprofile-kernel vs. notrace in ppc64(le) Linux kernels Torsten Duwe
2015-09-26 14:52 ` Segher Boessenkool
2015-09-26 23:03 ` Anton Blanchard
2015-09-27 11:06 ` Torsten Duwe [this message]
2015-09-28 0:08 ` Stewart Smith
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=20150927110633.GA9572@lst.de \
--to=duwe@lst.de \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.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 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.