From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13701 invoked by alias); 9 May 2002 21:36:54 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 13694 invoked from network); 9 May 2002 21:36:53 -0000 Received: from unknown (HELO inet1.ywave.com) (65.161.32.36) by sources.redhat.com with SMTP; 9 May 2002 21:36:53 -0000 Received: from there (unknown [12.144.140.96]) by inet1.ywave.com (Postfix) with SMTP id BC1AB2CAA4; Thu, 9 May 2002 14:32:34 -0700 (PDT) Content-Type: text/plain; charset="iso-8859-1" From: Tim Prince Reply-To: tprince@computer.org To: Daniel Berlin , Erik Schnetter Subject: [OT]Re: Benchmarks gcc 3.0.4 (soon 3.1) vs. Intel C++ 6.0 Date: Thu, 09 May 2002 14:43:00 -0000 Cc: gcc@gcc.gnu.org References: <20020509210223.4E7A72CB16@inet1.ywave.com> In-Reply-To: <20020509210223.4E7A72CB16@inet1.ywave.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020509213234.BC1AB2CAA4@inet1.ywave.com> X-SW-Source: 2002-05/txt/msg00706.txt.bz2 On Thursday 09 May 2002 14:02, Tim Prince wrote: > On Thursday 09 May 2002 09:01, Daniel Berlin wrote: > > On Thu, 9 May 2002, Erik Schnetter wrote: > > > Tim Prince 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) > > snipped > > > -erik > snipped >The > description of -ansi is certainly oblique. It assumes [the program is in] > conformance with ISO C89 [the main consequence being that typed aliasing > analysis can be employed, as with gcc -fstrict-aliasing]. My remarks here, while on medical leave from my employer, for whom I don't speak, have been taken as out of bounds, so I apologize. -- Tim Prince