public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeremy Sanders <jss@ast.cam.ac.uk>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: "S. Bosscher" <S.Bosscher@student.tudelft.nl>,
	"'gcc@gcc.gnu.org '" <gcc@gcc.gnu.org>
Subject: Re: benchmarking (or almabench)
Date: Tue, 22 Apr 2003 16:11:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.55.0304221615260.13881@xpc5.ast.cam.ac.uk> (raw)
In-Reply-To: <A59015DA-74D4-11D7-84FF-000A95A34564@dberlin.org>

On Tue, 22 Apr 2003, Daniel Berlin wrote:

> On Tuesday, April 22, 2003, at 11:08  AM, S. Bosscher wrote:
>
> > -march=pentium4 is known to pessimise code compared to -march=i686 for
> > some
> > benchmarks, see PR 8474.  Maybe you're seeing the same problem?
>
> Actually, if i had to guess, i'd put my money on the vectorization.
> Notice ICC vectorized two loops in his example, and obviously, we
> vectorized 0.
> :)

The intel compiler doesn't seem to vectorize with just "-O2" (by default
it should report whether it is using vectorization), and that's still 88%
faster than gcc. I can't absolutely confirm there's no vectorization as I
can't see a switch to turn it off.

icc says it's vectorizing when the P4 specific options are enabled (which
gcc can't do yet).

If I turn off any optimization on icc, then it's still faster than gcc!!!

xpc5:/<3>almabench-1.0.1/cpp> make
icc -o almabench.o -O0 -c almabench.cpp
icc -o almabench -O0 almabench.o
xpc5:/<3>almabench-1.0.1/cpp> time ./almabench
23.853u 0.134s 0:25.82 92.8%	0+0k 0+0io 121pf+0w

Jeremy

-- 
Jeremy Sanders <jss@ast.cam.ac.uk>   http://www-xray.ast.cam.ac.uk/~jss/
X-Ray Group, Institute of Astronomy, University of Cambridge, UK.
Public Key Server PGP Key ID: E1AAE053

  reply	other threads:[~2003-04-22 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 15:38 S. Bosscher
2003-04-22 16:00 ` Daniel Berlin
2003-04-22 16:11   ` Jeremy Sanders [this message]
2003-04-22 16:09 ` Jeremy Sanders
  -- strict thread matches above, loose matches on Subject: below --
2003-04-22 15:36 Jeremy Sanders

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=Pine.LNX.4.55.0304221615260.13881@xpc5.ast.cam.ac.uk \
    --to=jss@ast.cam.ac.uk \
    --cc=S.Bosscher@student.tudelft.nl \
    --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).