public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vladimir Makarov <vmakarov@redhat.com>
To: Chris Lattner <clattner@apple.com>
Cc: "gcc.gcc.gnu.org" <gcc@gcc.gnu.org>, Evan Cheng <evan.cheng@apple.com>
Subject: Re: New GCC releases comparison and comparison of GCC4.4 and LLVM2.5   on SPEC2000
Date: Tue, 12 May 2009 18:21:00 -0000	[thread overview]
Message-ID: <4A09BA64.1010601@redhat.com> (raw)
In-Reply-To: <CFB21785-5057-4A8B-9DC7-1C0CBC4D0EDB@apple.com>

Chris Lattner wrote:
>
> On May 12, 2009, at 6:56 AM, Vladimir Makarov wrote:
>
>> A few people asked me to do a new comparison of GCC releases and LLVM 
>> as the new GCC release and LLVM were out recently.
>>
>> You can find the comparison on http://vmakarov.fedorapeople.org/spec/
>>
>> The comparison for x86 (32-bit mode) was done on Pentium4 and  for 
>> x86_64 (64-bit mode) on Core I7.
>>
>> Some changes in the performance were big since GCC 3.2 and it is 
>> sometimes hard to see small changes on the posted graphs.   Therefore 
>> I put original tables used to generate the graphs.
>
> Looking at the llvm 2.5 vs gcc 4.4 comparison is very interesting, 
> thank you for putting this together Vladimir!  I find these numbers 
> particularly interesting because you're comparing simple options like 
> -O2 and -O3 instead of the crazy spec tuning mix :).  This is much 
> more likely to be representative of what real users will get on their 
> apps.
>
> Some random thoughts:
>
> 1. I have a hard time understanding the code size numbers.  Does 10% 
> mean that GCC is generating 10% bigger or 10% smaller code than llvm?
>
The change is reported relative to LLVM.  So 10% means that GCC 
generates 10% bigger code than LLVM and -10% means that GCC generates 
10% less code.
> 2. You change two variables in your configurations: micro architecture 
> and pointer size.  Would you be willing to run x86-32 Core i7 numbers 
> as well?  LLVM in particular is completely untuned for the (really old 
> and quirky) "netburst" architecture, but I'm interested to see how it 
> runs for you on more modern Core i7 or Core2 processors in 32-bit mode.
>
I used the same processor (P4) and options for x86 as for the GCC 
release comparison.  I did not know that LLVM is badly tuned for P4, 
sorry.  I could do the same comparison for x86 on Core i7 without 
specific tuning (there is no tuning for i7 yet) but it takes a lot of 
time.  May be it will be ready on next week.
> 3. Your SPEC FP benchmarks tell me two things: GCC 4.4's fortran 
> support is dramatically better than 4.2's (which llvm 2.5 uses), and 
> your art/mgrid hacks apparently do great stuff :).
>
> 4. Your SPEC INT numbers are more interesting to me.  It looks like 
> you guys have some significant wins in 175.vpr, 197.crafty, and other 
> benchmarks.  At some point, I'll have to see what you guys are doing :)
>
> Thanks for the info, great stuff!
>
> -Chris
>

  reply	other threads:[~2009-05-12 18:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 16:27 Vladimir Makarov
2009-05-12 18:05 ` Chris Lattner
2009-05-12 18:21   ` Vladimir Makarov [this message]
2009-05-12 19:25     ` Chris Lattner
2009-05-12 22:48       ` Rafael Espindola
2009-05-12 19:41     ` Vladimir Makarov
2009-05-13 12:11       ` Duncan Sands
2009-05-13 12:38         ` Richard Guenther
2009-05-13 12:55           ` Joseph S. Myers
2009-05-13 13:51           ` Duncan Sands
2009-05-26 12:27             ` Chris Lattner
2009-05-26 13:48               ` Vincent Lefevre
2009-05-28 23:00               ` Joseph S. Myers
2009-05-13 20:06         ` Evan Cheng
2009-05-12 18:29   ` Joseph S. Myers
2009-05-12 18:42     ` Vladimir Makarov
2009-05-13  8:44     ` Andi Kleen
2009-05-13  9:56       ` Jakub Jelinek
2009-05-13 11:32       ` Paolo Bonzini
2009-05-13 11:35         ` Paolo Bonzini
2009-05-13 12:07         ` Andi Kleen
2009-05-13 12:23           ` Steven Bosscher
2009-05-13 12:27             ` Dave Korn
2009-05-13 15:14           ` Paolo Bonzini
2009-05-13 16:16         ` Vladimir Makarov
2009-05-13 17:59           ` Jan Hubicka
2009-05-13 18:11             ` Michael Meissner
2009-05-15 20:19           ` Toon Moene
2009-05-13  6:42   ` Steven Bosscher
2009-05-13  7:33     ` Paolo Bonzini

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=4A09BA64.1010601@redhat.com \
    --to=vmakarov@redhat.com \
    --cc=clattner@apple.com \
    --cc=evan.cheng@apple.com \
    --cc=gcc@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).