public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it>
To: Joe Buck <jbuck@synopsys.COM>
Cc: gcc@gcc.gnu.org
Subject: Re: compiling linux kernels with GCC 3.0
Date: Wed, 10 Oct 2001 16:19:00 -0000	[thread overview]
Message-ID: <3BC4D749.B95DA8F@unitus.it> (raw)
In-Reply-To: <200110102222.PAA08822@atrus.synopsys.com>

Joe Buck wrote:

> for a discussion, test conditions, caveats, etc.  To jump straight to
> the significant results:
>
> http://www.suse.de/~aj/SPEC/reference/gcc-2.95.3.SuSE/CINT2000.048.html
> http://www.suse.de/~aj/SPEC/reference/gcc-3.0/CINT2000.186.html
> http://www.suse.de/~aj/SPEC/reference/gcc-3.0.1/CINT2000.185.html
>
> The trend is right, 2.95.3 < 3.0 < 3.0.1.
>
> The test platform is an AMD Athlon 1.133Ghz box.

First, thanks for the interesting summary.
One question: do you have reasons to believe that the same (nice!) trends holds
true also for Intel cpu's?
I'm asking this because recently I noticed some disappointing performance
regressions due to partial register stalls. For instance:

    http://gcc.gnu.org/ml/gcc/2001-09/msg00217.html

Privately, Jan Hubicka explained that partial register issues are some times
very difficult to sort out on the current x86 backend.

Thanks,
Paolo.


  reply	other threads:[~2001-10-10 16:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10  5:37 Alan Lehotsky
2001-10-10  7:22 ` Florian Weimer
2001-10-10  9:04   ` Josh McKinney
2001-10-10  9:26 ` Linus Torvalds
2001-10-10 11:09   ` Joe Buck
2001-10-10 11:23     ` Linus Torvalds
2001-10-10 15:23       ` Joe Buck
2001-10-10 16:19         ` Paolo Carlini [this message]
2001-10-10 16:58           ` Richard Henderson
2001-10-10 17:09             ` Paolo Carlini
2001-10-10 17:12               ` Richard Henderson
2001-10-10 19:03               ` Tim Prince
2001-10-10 15:39       ` Matthew Woodcraft
2001-10-10 11:40   ` Mark Mitchell
2001-10-10 14:01     ` Paolo Carlini
2001-10-10 14:15       ` Mark Mitchell
2001-10-10 14:54         ` Paolo Carlini
2001-10-10 15:57       ` Joe Buck
2001-10-10 11:23 Reichelt

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=3BC4D749.B95DA8F@unitus.it \
    --to=pcarlini@unitus.it \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.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).