From: Marc Gonzalez-Sigler <marc.gonzalez-sigler@inria.fr>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Pro64-based GPLed compiler
Date: Fri, 01 Jul 2005 08:48:00 -0000 [thread overview]
Message-ID: <42C50369.804@inria.fr> (raw)
In-Reply-To: <42C470EB.7000506@redhat.com>
Vladimir Makarov wrote:
> I heard a lot of this compiler and expected a better results for it.
> Using -O2 -mtune=nocona for gcc4 and -O2 -mtune=em64t for open64 on
> em64t machine in 32-bit mode, I found preliminarily that pathscale
> compiler generates about 10% worse and 30% larger code (text segment)
> for SPECInt2000. It is also 70% slower than gcc4. I just hope results
> for 64-bit mode, amd machine, or SPECFP2000 are better.
You might want to give the official release a try. (In other words,
I don't think it's safe to use our "distribution" to judge EKOPath.)
http://www.pathscale.com/ekopath.html
AFAIU, LNO is not performed at -O2, so you should use -O3.
And, if I managed to build the IPA module, you should use -Ofast.
If you are interested, I can run SPECint2000 on a 3.0 GHz Northwood
core, and report the results here.
Finally, as James noted, the performance on AMD CPUs should be
higher than that on Intel CPUs.
--
Regards, Marc
next prev parent reply other threads:[~2005-07-01 8:48 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
2005-07-01 8:48 ` Marc Gonzalez-Sigler [this message]
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=42C50369.804@inria.fr \
--to=marc.gonzalez-sigler@inria.fr \
--cc=gcc@gcc.gnu.org \
--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).