From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9687 invoked by alias); 14 Feb 2003 21:09:03 -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 9661 invoked by uid 48); 14 Feb 2003 21:09:03 -0000 Date: Fri, 14 Feb 2003 21:09:00 -0000 Message-ID: <20030214210903.9660.qmail@sources.redhat.com> To: eckmann@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jean-pierre.eckmann@physics.unige.ch, toon@gcc.gnu.org From: toon@gcc.gnu.org Reply-To: toon@gcc.gnu.org, eckmann@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jean-pierre.eckmann@physics.unige.ch, toon@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: fortran/8445: optimizer bug? X-SW-Source: 2003-02/txt/msg00624.txt.bz2 List-Id: Synopsis: optimizer bug? State-Changed-From-To: feedback->closed State-Changed-By: toon State-Changed-When: Fri Feb 14 21:09:02 2003 State-Changed-Why: This is a classical case of x86-ism. The symptoms are: 1. Comparison of two floating point values, one computed and one stored. 2. Works on all architectures except x86. 3. Problem goes away when adding -ffloat-store to the compiler options. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8445