From: Jim Blandy <jimb@red-bean.com>
To: Laurent GUERBY <laurent@guerby.net>
Cc: Andrew Haley <aph@redhat.com>,
Richard Earnshaw <rearnsha@gcc.gnu.org>,
Bernd Schmidt <bernds_cb1@t-online.de>,
Daniel Jacobowitz <drow@false.org>,
Ian Lance Taylor <ian@airs.com>,
Robert Dewar <dewar@adacore.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Directly generating binary code [Was Re: Link-time optimzation]
Date: Fri, 18 Nov 2005 17:41:00 -0000 [thread overview]
Message-ID: <8f2776cb0511180941l590b693fyedd781954ce4d7fc@mail.gmail.com> (raw)
In-Reply-To: <1132315408.6774.1711.camel@pc.site>
On 11/18/05, Laurent GUERBY <laurent@guerby.net> wrote:
> On Fri, 2005-11-18 at 11:40 +0000, Andrew Haley wrote:
> > A nightmare scenario is debugging the compiler when its behaviour
> > changes due to using "-S". Assembly source is something that we
> > maintainers use more than anyone else.
>
> If we go the direct generation route, I think it would be more
> efficient (if possible) to add whatever extra information is needed in
> the object file (like the asm template string, compiler comments, ...)
> so that object code dumper will get it back to you on request. So skip
> the -S altogether, always use the object dumper to "look at assembly".
The point Andrew's raising here is that you are replacing an
intermediate form that is very useful for isolating problems --- the
assembly language file --- with an in-core form that is much more
difficult to inspect.
And there are various side consequences: for example, you know the
compiler isn't going to go and tweak the assembly-language file you're
looking at, because it's exited. But with an in-core representation
(and a non-type-safe language like C), compiler bugs can still be
mangling the assembly code "after" it's been generated.
For a 2% speedup? That hasn't been carefully measured?
next prev parent reply other threads:[~2005-11-18 17:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 22:26 Link-time optimzation 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 [this message]
2005-11-18 18:35 ` Link-time optimzation Mike Stump
2005-11-18 2:33 ` 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
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=8f2776cb0511180941l590b693fyedd781954ce4d7fc@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=aph@redhat.com \
--cc=bernds_cb1@t-online.de \
--cc=dewar@adacore.com \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=laurent@guerby.net \
--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).