public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: Steven Bosscher <stevenb@suse.de>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Compilation performance comparison of gcc3.4.1 and gcc3.5.0  2004-08-30 on MICO sources
Date: Wed, 01 Sep 2004 07:18:00 -0000	[thread overview]
Message-ID: <413578D7.5040909@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0408311251230.1006-100000@thinkpad.gardas.net>

3.4.1 seems to have a problem with the expander at -O2:

>  expand                :   8.79 (26%) usr   0.01 ( 0%) sys   8.90 (24%) wall

So this 3.4.1 bug is somehow work around by gimplification and tree 
optimization, and this masks the 40% difference (which would still be 
there at -O2 if it weren't for the improvement in expander time).

Paolo

  reply	other threads:[~2004-09-01  7:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  9:58 Karel Gardas
2004-08-31 10:12 ` Steven Bosscher
2004-08-31 10:28   ` Karel Gardas
2004-08-31 10:44     ` Paolo Bonzini
2004-08-31 10:46       ` Karel Gardas
2004-08-31 10:49         ` Steven Bosscher
2004-08-31 11:00           ` Paolo Bonzini
2004-08-31 11:24             ` Steven Bosscher
2004-08-31 19:30               ` Mike Stump
2004-08-31 12:48             ` Karel Gardas
2004-09-01  7:18               ` Paolo Bonzini [this message]
2004-08-31 10:55         ` Steven Bosscher
2004-08-31 13:57           ` Karel Gardas
2004-09-01 11:18 ` Giovanni Bajo
2004-09-02  9:41   ` Karel Gardas
2004-09-02 20:32     ` Compilation performance comparison of gcc3.4.1 and gcc3.5.02004-08-30 " Giovanni Bajo
2004-09-04  7:35       ` Karel Gardas
2004-09-02  9:44   ` Compilation performance comparison of gcc3.4.1 and gcc3.5.0 2004-08-30 " Karel Gardas

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=413578D7.5040909@gnu.org \
    --to=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kgardas@objectsecurity.com \
    --cc=stevenb@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).