From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, kyle@mcmartin.ca
Subject: Re: [PATCH] parisc: add ftrace (function and graph tracer) functionality
Date: Tue, 10 Feb 2009 10:24:38 +0800 [thread overview]
Message-ID: <4990E566.3020500@tausq.org> (raw)
In-Reply-To: <20090210021101.2118F4EDA@hiauly1.hia.nrc.ca>
My memory is fuzzy and I had to dig through the archives a bit, but I
seem to recall that it used to be that -pg will not work WITHOUT
-ffunction-sections on 32-bit, because the call to _mcount was done
using b,l. Dave and I fixed this in gcc in 2003 though.
I did find another thread about this here:
http://gcc.gnu.org/ml/gcc-help/2008-11/msg00128.html
The followup replies from Ian Taylor and Jeff Law concurs with what you
said below, but it looks like nothing has been done (yet?)
randolph
John David Anglin wrote:
>> It will currently only work with 64bit kernels, because the gcc options -pg
>> and -ffunction-sections can't be enabled at the same time and -ffunction-sections
>> is still needed to be able to link 32bit kernels.
>>
>
> I have done some testing. As far as I can tell, -pg works with
> -ffunction-sections on hppa-unknown-linux-gnu and hppa64-hp-hpux11.
> hppa2.0w-hp-hpux11 doesn't support -ffunction-sections. So, I think
> we should propose that the code that disables -ffunction-sections
> with -pg be removed.
>
> Dave
>
next prev parent reply other threads:[~2009-02-10 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 23:43 [PATCH] parisc: add ftrace (function and graph tracer) functionality Helge Deller
2009-02-10 2:10 ` John David Anglin
2009-02-10 2:24 ` Randolph Chung [this message]
2009-02-10 2:48 ` John David Anglin
2009-02-10 20:56 ` Helge Deller
2009-02-11 2:43 ` John David Anglin
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=4990E566.3020500@tausq.org \
--to=randolph@tausq.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.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.