From: Karel Gardas <kgardas@objectsecurity.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Paolo Bonzini <bonzini@gnu.org>, 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: Tue, 31 Aug 2004 13:57:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.43.0408311544570.1006-100000@thinkpad.gardas.net> (raw)
In-Reply-To: <200408311243.11380.stevenb@suse.de>
On Tue, 31 Aug 2004, Steven Bosscher wrote:
> On Tuesday 31 August 2004 12:28, Karel Gardas wrote:
> > On Tue, 31 Aug 2004, Paolo Bonzini wrote:
> > > >>>1) typecode.cc: 40% regression on O1 while 7% speedup on O2
> > > >>
> > > >>Can you show us the time report for the 40% regression?
> > >
> > > Also for 3.4.1?
> >
> > Sure!
>
> Hmm... No obvious hot spots eh?
>
BTW: gcc3.4.1 consumes about 66MB of RAM to compile this file, while trunk
consumes about 98MB to compile it and also testing box is pIII mobile with
only 256kb cache, so higher memory usage also might add something to the
regression...
Karel
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
next prev parent reply other threads:[~2004-08-31 13:47 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
2004-08-31 10:55 ` Steven Bosscher
2004-08-31 13:57 ` Karel Gardas [this message]
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=Pine.LNX.4.43.0408311544570.1006-100000@thinkpad.gardas.net \
--to=kgardas@objectsecurity.com \
--cc=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--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).