public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Erik Schnetter <schnetter@uni-tuebingen.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Benchmarks gcc 3.0.4 (soon 3.1) vs. Intel C++ 6.0
Date: Thu, 09 May 2002 09:33:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0205091146191.8286-100000@dberlin.org> (raw)
In-Reply-To: <200205091542.g49Fg9u13279@lilypond.tat.physik.uni-tuebingen.de>

On Thu, 9 May 2002, Erik Schnetter wrote:

> Tim Prince <tprince at computer dot org> wrote:
> 
> > icc's equivalent to -fstrict-aliasing is -ansi.  It's not a default.
> 
> I couldn't find anything about aliasing in the description of "-ansi".  

It does what he says, however, i can prove it through option dumps (it 
turns on P2OPT_disam_assume_ansi_c)
> However, icc does have a "-falias" option (which is also not the default).  
> The description of "-falias" is unfortunately unusable.

You mean -fno-alias and -fno-fnalias, i thinks.

If you want to see the aliasing/intermediate code dumps for intel's 
compiler, so you can watch what it does at each stage, "-mIPOPT_trace=-1 
-mP1OPT_il0_trace=-1 -mP2OPT_il0_list_source_lines=-1 -mP2OPT_il0_dump=0 
-mIPOPT_opt_trace=-1"  will suffice.

If you want the debug options to print the mod-ref sets and whatnot, let 
me know.


> 
> -erik
> 
> 

  parent reply	other threads:[~2002-05-09 16:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  8:50 Erik Schnetter
2002-05-09  9:04 ` Tim Prince
2002-05-09  9:33 ` Daniel Berlin [this message]
2002-05-09 14:08   ` Tim Prince
2002-05-09 14:43     ` [OT]Re: " Tim Prince
  -- strict thread matches above, loose matches on Subject: below --
2002-05-09 15:56 Robert Dewar
2002-05-09  9:54 kelley.r.cook
2002-05-09 10:45 ` law
2002-05-09  5:50 Scott Robert Ladd
2002-05-09  6:21 ` Jan Hubicka
2002-05-09  6:33   ` Scott Robert Ladd
2002-05-09  7:04     ` Jan Hubicka
2002-05-09  7:12       ` Scott Robert Ladd
2002-05-09  7:37         ` Jan Hubicka
2002-05-09  7:41       ` Jack Lloyd
2002-05-09  8:42         ` Tim Prince
2002-05-09  8:48         ` Scott Robert Ladd
2002-05-09 11:22         ` law
2002-05-10 14:17           ` Jack Lloyd
2002-05-09  7:41   ` Tim Prince
2002-05-09  7:48     ` Tim Prince

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.44.0205091146191.8286-100000@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=schnetter@uni-tuebingen.de \
    /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).