From: Andi Kleen <andi@firstfloor.org>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Prague GCC folks meeting summary report
Date: Fri, 02 Oct 2009 00:00:00 -0000 [thread overview]
Message-ID: <87d456u0l1.fsf@basil.nowhere.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0909241234100.4520@zhemvz.fhfr.qr> (Richard Guenther's message of "Thu, 24 Sep 2009 12:35:06 +0200 (CEST)")
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.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-10-02 0:00 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 [this message]
2009-10-02 0:21 ` Joe Buck
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=87d456u0l1.fsf@basil.nowhere.org \
--to=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).