From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14320 invoked by alias); 12 Feb 2003 16:46:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 14305 invoked by uid 71); 12 Feb 2003 16:46:00 -0000 Date: Wed, 12 Feb 2003 16:46:00 -0000 Message-ID: <20030212164600.14304.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Richard Earnshaw Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized Reply-To: Richard Earnshaw X-SW-Source: 2003-02/txt/msg00528.txt.bz2 List-Id: The following reply was made to PR optimization/9052; it has been noted by GNATS. From: Richard Earnshaw To: Steven Bosscher Cc: Richard.Earnshaw@arm.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, phama@webjockey.net, Eric Botcazou Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized Date: Wed, 12 Feb 2003 16:36:37 +0000 > > So in summary, almost certainly "not a bug". > > Pfewww, good. > > Still it is a change in behavior of the generated code. Should it be > documented? What would you document? "Our optimizations are better than they used to be, so if your code is broken, we're more likely to catch you out"? In reality this is not much different from a expression like x[i++] = y[i++] + 1; It's ill-defined code, so anything can happen. R.