From: Mike Stump <mrs@apple.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Ian Lance Taylor <ian@airs.com>, Robert Dewar <dewar@adacore.com>,
Richard Earnshaw <rearnsha@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Link-time optimzation
Date: Fri, 18 Nov 2005 18:35:00 -0000 [thread overview]
Message-ID: <7F7C7F6E-5E10-48FD-8333-CB3267336300@apple.com> (raw)
In-Reply-To: <20051118021329.GA31135@nevyn.them.org>
On Nov 17, 2005, at 6:13 PM, Daniel Jacobowitz wrote:
> Also, please keep in mind that generating and then assembling debug
> info takes a huge amount of I/O relative to code size. I'd expect
> much
> more than 1% saving the write-out and write-in on -g.
I'd hope that we can contribute code to eliminate this, so, it might
be possible to not consider any benefit this would have in the
current decision making.
compiler -> debug info repository -> gdb (side stepping the linker,
the assembler)
next prev parent reply other threads:[~2005-11-18 18:35 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 22:26 Mark Mitchell
2005-11-16 22:41 ` Andrew Pinski
2005-11-16 22:58 ` Andrew Pinski
2005-11-17 0:02 ` Andrew Pinski
2005-11-17 0:25 ` Andrew Pinski
2005-11-17 0:52 ` Tom Tromey
2005-11-17 0:26 ` Giovanni Bajo
2005-11-17 0:32 ` Daniel Berlin
2005-11-17 9:04 ` Giovanni Bajo
2005-11-17 16:25 ` Kenneth Zadeck
2005-11-17 1:20 ` Richard Henderson
2005-11-17 1:28 ` Mark Mitchell
2005-11-17 1:31 ` Daniel Jacobowitz
2005-11-17 3:35 ` Jeffrey A Law
2005-11-17 14:09 ` Daniel Berlin
2005-11-17 14:48 ` mathieu lacage
2005-11-17 11:41 ` Richard Earnshaw
2005-11-17 21:40 ` Ian Lance Taylor
2005-11-17 23:10 ` Robert Dewar
2005-11-17 23:42 ` Ian Lance Taylor
2005-11-18 2:13 ` Daniel Jacobowitz
2005-11-18 9:29 ` Bernd Schmidt
2005-11-18 11:19 ` Robert Dewar
2005-11-18 11:29 ` Richard Earnshaw
2005-11-18 11:40 ` Directly generating binary code [Was Re: Link-time optimzation] Andrew Haley
2005-11-18 12:04 ` Laurent GUERBY
2005-11-18 17:41 ` Jim Blandy
2005-11-18 18:35 ` Mike Stump [this message]
2005-11-18 2:33 ` Link-time optimzation Dale Johannesen
2005-11-18 3:11 ` Geert Bosch
2005-11-18 18:43 ` Mike Stump
2005-11-18 18:30 ` Mike Stump
2005-11-17 15:54 ` Kenneth Zadeck
2005-11-17 16:41 ` Jan Hubicka
2005-11-18 16:31 ` Michael Matz
2005-11-18 17:04 ` Steven Bosscher
2005-11-18 17:29 ` Michael Matz
2005-11-18 17:24 ` Nathan Sidwell
2005-11-17 1:43 ` Gabriel Dos Reis
2005-11-17 1:53 ` Andrew Pinski
2005-11-17 2:39 ` Kean Johnston
2005-11-17 5:53 ` Ian Lance Taylor
2005-11-17 13:08 ` Ulrich Weigand
2005-11-17 21:42 ` Ian Lance Taylor
2005-11-17 16:17 ` Kenneth Zadeck
2005-11-17 0:52 Chris Lattner
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=7F7C7F6E-5E10-48FD-8333-CB3267336300@apple.com \
--to=mrs@apple.com \
--cc=dewar@adacore.com \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=rearnsha@gcc.gnu.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 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).