From: Joe Buck <Joe.Buck@synopsys.COM>
To: Andi Kleen <andi@firstfloor.org>
Cc: Richard Guenther <rguenther@suse.de>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Prague GCC folks meeting summary report
Date: Fri, 02 Oct 2009 00:21:00 -0000 [thread overview]
Message-ID: <20091002002057.GC13104@synopsys.com> (raw)
In-Reply-To: <87d456u0l1.fsf@basil.nowhere.org>
On Thu, Oct 01, 2009 at 05:00:10PM -0700, Andi Kleen wrote:
> Richard Guenther <rguenther@suse.de> writes:
> >
> > The wish for more granular and thus smaller debug information (things like
> > -gfunction-arguments which would properly show parameter values
> > for backtraces) was brought up. We agree that this should be addressed at a
> > tools level, like in strip, not in the compiler.
>
> Is that really the right level? In my experience (very roughly) -g can turn gcc from
> CPU bound to IO bound (especially considering distributed compiling appraches),
> and dropping unnecessary information in external tools would make the IO penalty even
> worse.
Certainly life can suck when building large C++ apps with -g in an NFS
environment. Assuming we can generate tons of stuff and strip it later
might not be best.
next prev parent reply other threads:[~2009-10-02 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 10:35 Richard Guenther
2009-09-24 15:26 ` Jeff Law
2009-09-24 16:00 ` Joseph S. Myers
2009-09-24 16:34 ` Joseph S. Myers
2009-09-24 21:26 ` Richard Guenther
2009-09-25 19:14 ` Kevin P. Fleming
2009-10-02 0:00 ` Andi Kleen
2009-10-02 0:21 ` Joe Buck [this message]
2009-10-02 9:45 ` Richard Guenther
2009-10-02 13:30 ` Andi Kleen
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=20091002002057.GC13104@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=andi@firstfloor.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).