From: Helge Deller <deller@gmx.de>
To: Carlos O'Donell <carlos@systemhalted.org>,
John David Anglin <dave@hiauly1.hia.nrc.ca>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: FUNCTION_TRACER and parisc kernel
Date: Sat, 07 Feb 2009 02:19:04 +0100 [thread overview]
Message-ID: <498CE188.60308@gmx.de> (raw)
Hi Carlos, Dave & parisc-linux mailing list,
I just started looking into implementing function tracer functionality
into the parisc kernel (http://cateee.net/lkddb/web-lkddb/FUNCTION_TRACER.html).
While doing so, I noticed that gcc issues lots of warnings like this one:
CC arch/parisc/lib/iomap.o
cc1: warning: -ffunction-sections disabled; it makes profiling impossible
So it seems that this statement in arch/parisc/Makefile:
# Without this, "ld -r" results in .text sections that are too big
# (> 0x40000) for branches to reach stubs.
cflags-y += -ffunction-sections
breaks with the -pg compile option which is needed for function tracing.
Some searching with google brought up this thread:
http://gcc.gnu.org/ml/gcc-help/2008-11/msg00128.html
and esp. this answer:
http://gcc.gnu.org/ml/gcc-help/2008-11/msg00141.html
Or this thread:
http://osdir.com/ml/linux.debian.ports.hppa/2005-06/msg00045.html
Since it's late I felt too tired to look deeply into glibc and gcc myself and
just thought I should ask here: Do you see any chance that -pg and -ffunction-sections
could work together on hppa/linux?
Helge
PS: I assume my latest patches to fix loading of xfs modules only worked
because we compile the kernel with -ffunction-sections by default. Disabling
-ffunction-sections will then probably bring back the module loading bug... :-(
next reply other threads:[~2009-02-07 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 1:19 Helge Deller [this message]
2009-02-07 3:25 ` FUNCTION_TRACER and parisc kernel John David Anglin
2009-02-07 18:32 ` John David Anglin
2009-02-07 19:05 ` Helge Deller
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=498CE188.60308@gmx.de \
--to=deller@gmx.de \
--cc=carlos@systemhalted.org \
--cc=dave@hiauly1.hia.nrc.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.