From: Sam Ravnborg <sam@ravnborg.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: RFC: How to handle function tracing, frame pointers and -mfentry?
Date: Sat, 28 Apr 2012 11:11:08 +0200 [thread overview]
Message-ID: <20120428091108.GA6847@merkur.ravnborg.org> (raw)
In-Reply-To: <20120428085028.GA6507@merkur.ravnborg.org>
On Sat, Apr 28, 2012 at 10:50:28AM +0200, Sam Ravnborg wrote:
> >
> > I just measured and a null compile (nothing changes) of a current
> > tree calls "gcc" 141 times.
> Something is wrong then which must be fixed.
> There are 55 uses of cc-option in */x86/*
> And only 7 uses of cc-option in the top-level Makefile.
>
> So it looks like we evalute the same assignmet twice or more.
"make defconfig" in my box calls gcc 50 times.
This looks much closer to the actual usage of cc-option in the
above mentioned files.
How did you manage to achieve 144 calls to gcc?
Any specific configuration that triggers this?
Sam
next prev parent reply other threads:[~2012-04-28 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 18:46 RFC: How to handle function tracing, frame pointers and -mfentry? Steven Rostedt
2012-04-27 19:43 ` Steven Rostedt
2012-04-27 20:27 ` Sam Ravnborg
2012-04-27 20:31 ` H. Peter Anvin
2012-04-27 20:57 ` Steven Rostedt
2012-04-27 21:11 ` H. Peter Anvin
2012-04-27 21:27 ` Steven Rostedt
2012-04-28 8:36 ` Andi Kleen
2012-04-28 8:50 ` Sam Ravnborg
2012-04-28 9:11 ` Sam Ravnborg [this message]
2012-04-28 12:16 ` Andi Kleen
2012-04-28 16:34 ` H. Peter Anvin
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=20120428091108.GA6847@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fweisbec@gmail.com \
--cc=hpa@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mmarek@suse.cz \
--cc=rostedt@goodmis.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.