From: Alexandre Oliva <aoliva@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Andrew MacLeod <amacleod@redhat.com>,
Ian Lance Taylor <iant@google.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [trunk<-vta] Re: [vtab] Permit coalescing of user variables
Date: Wed, 03 Jun 2009 19:15:00 -0000 [thread overview]
Message-ID: <or8wk9ku28.fsf@free.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <84fc9c000906031118l1986d079r2a333d87fcde6e65@mail.gmail.com> (Richard Guenther's message of "Wed\, 3 Jun 2009 20\:18\:40 +0200")
On Jun 3, 2009, Richard Guenther <richard.guenther@gmail.com> wrote:
> Btw, _is_ there really a such big effect with enabling the extra coalescing?
I'm pretty sure I even posted SPEC results back when I first proposed
these changes.
I remember there was a huge effect in compile time for some
machine-generated sources. Surely if enabling coalescing for inlined
variables had such a huge effect, enabling it for non-inlined variables
would have an even larger effect.
Difference in performance was nothing to write home about, but when
you're trying to squeeze the last bit of performance from a program,
losing it to debug info you're not even interested in doesn't speak well
of GCC.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
next prev parent reply other threads:[~2009-06-03 19:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 19:05 Alexandre Oliva
2007-10-02 9:15 ` Richard Guenther
2007-10-02 21:02 ` Andrew MacLeod
2007-10-03 1:11 ` Alexandre Oliva
2007-10-09 21:32 ` Alexandre Oliva
2009-06-01 7:39 ` [trunk<-vta] " Alexandre Oliva
2009-06-01 7:44 ` Alexandre Oliva
2009-06-01 16:11 ` Ian Lance Taylor
2009-06-01 17:35 ` Andrew MacLeod
2009-06-01 19:23 ` Alexandre Oliva
2009-06-02 9:54 ` Richard Guenther
2009-06-02 21:42 ` Alexandre Oliva
2009-06-03 1:13 ` Andrew MacLeod
2009-06-03 10:18 ` Richard Guenther
2009-06-03 17:43 ` Alexandre Oliva
2009-06-03 18:06 ` Daniel Jacobowitz
2009-06-03 19:17 ` Alexandre Oliva
2009-06-03 19:45 ` Daniel Jacobowitz
2009-06-03 21:42 ` Alexandre Oliva
2009-06-03 18:18 ` Richard Guenther
2009-06-03 19:15 ` Alexandre Oliva [this message]
2009-06-03 19:50 ` Richard Guenther
2009-06-03 19:53 ` Ian Lance Taylor
2009-10-13 21:27 ` Alexandre Oliva
2011-06-04 12:45 ` Alexandre Oliva
2011-06-04 13:02 ` Jakub Jelinek
2011-06-05 21:07 ` Alexandre Oliva
2011-06-06 2:42 ` Alexandre Oliva
2012-04-09 5:56 ` Alexandre Oliva
2012-06-13 8:34 ` Alexandre Oliva
2012-06-13 9:48 ` Richard Guenther
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=or8wk9ku28.fsf@free.oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=richard.guenther@gmail.com \
/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).