This is the mail archive of the
mailing list for the GCC project.
Re: Benchmarks gcc 3.0.4 (soon 3.1) vs. Intel C++ 6.0
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Erik Schnetter <schnetter at uni-tuebingen dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 9 May 2002 12:01:15 -0400 (EDT)
- Subject: Re: Benchmarks gcc 3.0.4 (soon 3.1) vs. Intel C++ 6.0
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