From: Paolo Bonzini <bonzini@gnu.org>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Chris Lattner <clattner@apple.com>,
Vladimir Makarov <vmakarov@redhat.com>,
"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: Wed, 13 May 2009 07:33:00 -0000 [thread overview]
Message-ID: <4A0A6BD5.6070406@gnu.org> (raw)
In-Reply-To: <571f6b510905121509g3bff95a0g9872117d278e59be@mail.gmail.com>
>> 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 :).
>
> Something like the "art hack" is in ipa-struct-reorg, but it is not
> enabled at any level. If gcc outperforms llvm on art by much, it's
> more likely that some important opportunities for art are being
> overlooked by llvm.
>
> There also isn't anything special done for mgrid, except predictive
> commoning (CSE around loops) which is not a hack, in the sense it is
> helpful for a lot of numerical code and triggers several times in
> things like generic Fortran blas/lapack routines.
Indeed, we have a couple of benchmark-inspired optimizations for
SPEC2006 (division/modulo power-of-two, see PR26026; and ifcombine), and
we optimize MATMUL (TRANSPOSE (A), B) which helps galgel a lot. But
both of this may trigger quite a lot on other code, and LLVM also
benefits from the galgel one :-) because it's done in the front-end.
Paolo
prev parent reply other threads:[~2009-05-13 6:42 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
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 [this message]
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=4A0A6BD5.6070406@gnu.org \
--to=bonzini@gnu.org \
--cc=clattner@apple.com \
--cc=evan.cheng@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=stevenb.gcc@gmail.com \
--cc=vmakarov@redhat.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).