From: Marc Gonzalez-Sigler <marc.gonzalez-sigler@inria.fr>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Pro64-based GPLed compiler
Date: Fri, 01 Jul 2005 09:24:00 -0000 [thread overview]
Message-ID: <42C50BBF.7040207@inria.fr> (raw)
In-Reply-To: <1120183311.17986.7.camel@linux-009002243055>
Daniel Berlin wrote:
> On Thu, 2005-06-30 at 17:17 -0700, James E Wilson wrote:
>
>> Their web pages primarily talk about the 64-bit performance on AMD
>> systems. Maybe they aren't well tuned for 32-bit performance and/or
>> Intel parts. Anyways, from what Daniel Berlin mentioned, it may be that
>> the tree-ssa stuff in gcc4.x has negated much of their earlier advantage.
>
> I would not be surprised if they kick the crap out of us when it comes
> to numerical fortran or something, but for regular c code, i'd not
> expect more than 10-20% difference, max.
On an FX-57, EKOPath is close to icc for SPECint2000:
http://www.spec.org/osg/cpu2000/results/res2005q2/cpu2000-20050613-04264.html
http://www.spec.org/osg/cpu2000/results/res2005q2/cpu2000-20050613-04262.html
icc on WinXP SPECint2000 = 1970
pathcc on Linux SPECint2000 = 1929
Do you have a SPECint2000 breakdown for gcc tree-ssa on Linux?
The dev's summit mentions SPECint2000 results, but I didn't find what
I was looking for.
http://www.gccsummit.org/2005/2005-GCC-Summit-Proceedings.pdf
--
Regards, Marc
next prev parent reply other threads:[~2005-07-01 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 15:46 Marc Gonzalez-Sigler
2005-06-29 18:01 ` Vladimir Makarov
2005-06-29 21:28 ` Marc
2005-06-30 1:19 ` Daniel Berlin
2005-06-30 21:46 ` James E Wilson
2005-06-30 22:23 ` Vladimir Makarov
2005-06-30 22:30 ` Daniel Berlin
2005-07-01 0:17 ` James E Wilson
2005-07-01 2:02 ` Daniel Berlin
2005-07-01 9:24 ` Marc Gonzalez-Sigler [this message]
2005-07-01 8:48 ` Marc Gonzalez-Sigler
2005-07-01 6:58 Joost VandeVondele
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=42C50BBF.7040207@inria.fr \
--to=marc.gonzalez-sigler@inria.fr \
--cc=dberlin@dberlin.org \
--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).