From: Andi Kleen <andi@firstfloor.org>
To: Richard Guenther <rguenther@suse.de>
Cc: Joe Buck <Joe.Buck@synopsys.COM>,
Andi Kleen <andi@firstfloor.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Prague GCC folks meeting summary report
Date: Fri, 02 Oct 2009 13:30:00 -0000 [thread overview]
Message-ID: <20091002133028.GM1656@one.firstfloor.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0910021143030.4520@zhemvz.fhfr.qr>
> To make the above work first the external tools have to add the
> capabilities, just implementing it in GCC doesn't work for us.
Ok, but there's more to building software, than just building rpms.
For example I can definitely see a common use case where a program
is built with line number and unwinding information, but not with types.
Or types are only generated partially using a special "debug file".
And for that it would be best if gcc simply didn't generate unnecessary
information and minimizes IO and disk space requirements.
iirc there was even a patch in this direction from Frank Ch. Eigler
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-10-02 13:30 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
2009-10-02 9:45 ` Richard Guenther
2009-10-02 13:30 ` Andi Kleen [this message]
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=20091002133028.GM1656@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Joe.Buck@synopsys.COM \
--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).