From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14486 invoked by alias); 29 Sep 2002 17:16:49 -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 14407 invoked from network); 29 Sep 2002 17:16:47 -0000 Received: from unknown (HELO nile.gnat.com) (205.232.38.5) by sources.redhat.com with SMTP; 29 Sep 2002 17:16:47 -0000 Received: by nile.gnat.com (Postfix, from userid 338) id 0E8E2F2CB6; Sun, 29 Sep 2002 13:16:46 -0400 (EDT) To: bkorb@pacbell.net, dewar@gnat.com Subject: Re: module level flags Cc: gcc@gcc.gnu.org, zack@codesourcery.com Message-Id: <20020929171646.0E8E2F2CB6@nile.gnat.com> Date: Sun, 29 Sep 2002 10:31:00 -0000 From: dewar@gnat.com (Robert Dewar) X-SW-Source: 2002-09/txt/msg01194.txt.bz2 <> Surely if you take this attitude you should just turn off aliasing analysis. Really we expect gcc to implement C by default, not C + "fixes" to the standard that Bruce Korb thinks are obviously correct. GCC is not "reserving the right to destroy the workings of a program", since this program simply does not meet the semantics of C. Just because you expect some program whose semantics is not defined by the standard to do something, does not mean that a C compiler wlil agree with your analysis. There are lots of respects in which people write non-standard C and expect it to work. This particular case seems to me to be one that should never have been expected to work (i.e. I don't see any formal definition of C that guarantees this program will work -- if I am wrong on this, please point out the document, but do not expect me to be impressed by what some individual *thinks* the language should be. That's not decisive :-) Robert Dewar