From: Devang Patel <dpatel@apple.com>
To: Jeremy Sanders <jss@ast.cam.ac.uk>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Scott Robert Ladd <coyote@coyotegulch.com>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Comparing Linux C and C++ Compilers: Benchmarks and Analysis
Date: Mon, 20 Sep 2004 20:44:00 -0000 [thread overview]
Message-ID: <76829D8A-0B3E-11D9-B83D-000393A91CAA@apple.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0409191459150.7275@xpc5.ast.cam.ac.uk>
On Sep 19, 2004, at 7:02 AM, Jeremy Sanders wrote:
> On Sat, 18 Sep 2004, Richard Guenther wrote:
>
>> You may want to check gcc 4.0s auto-vectorizing capabilities by using
>> -ftree-vectorize. I believe Intel compiler does this by default with
>> your optimization settings, and also unrolls loops where profitable
>> (-funroll-loops for all gcc versions). While I personally do not
>> have success with auto-vectorizing (neither with Intel nor with gcc),
>> loop unrolling shows very positive effects on my numerical codes.
>
> I tried compiling scimark with gcc 4 with -ftree-vectorize -msse2
> -fdump-tree-vect-stats and again with the lno branch. This was with a
> P4 on Fedora Core 2. Looking at the generated .vect files, it looked
> like gcc wasn't able to vectorize any of the loops in scimark, which
> is a bit diappointing. It's possible I didn't use it correctly I
> suppose.
Would it be possible to post what GCC emits in .vect file, using
-fdump-tree-vect-details option, for loops that you expect to get
vectorized (or loops that are vectorized by other compilers)?. If you
can provide preprocessed source file, I can try it on powerpc-darwin.
Thanks,
-
Devang
next prev parent reply other threads:[~2004-09-20 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-18 18:26 Scott Robert Ladd
2004-09-18 18:37 ` Richard Guenther
2004-09-18 20:42 ` Scott Robert Ladd
2004-09-19 14:55 ` Jeremy Sanders
2004-09-20 20:44 ` Devang Patel [this message]
2004-09-18 21:35 ` Andi Kleen
2004-09-18 23:19 ` Scott Robert Ladd
2004-09-18 23:46 ` Natros
2004-09-19 0:08 ` Scott Robert Ladd
2004-09-19 11:38 ` Kaveh R. Ghazi
2004-09-19 11:50 ` Scott Robert Ladd
2004-09-20 13:51 ` Kaveh R. Ghazi
2004-09-20 14:56 ` Scott Robert Ladd
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=76829D8A-0B3E-11D9-B83D-000393A91CAA@apple.com \
--to=dpatel@apple.com \
--cc=coyote@coyotegulch.com \
--cc=gcc@gcc.gnu.org \
--cc=jss@ast.cam.ac.uk \
--cc=richard.guenther@gmail.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).