From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15177 invoked by alias); 14 Mar 2003 11:32:55 -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 15158 invoked by uid 48); 14 Mar 2003 11:32:55 -0000 Date: Fri, 14 Mar 2003 11:32:00 -0000 Message-ID: <20030314113255.15157.qmail@sources.redhat.com> To: ac@m2000.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: ebotcazou@gcc.gnu.org Reply-To: ebotcazou@gcc.gnu.org, ac@m2000.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/10078: bad code generated with optimisation. X-SW-Source: 2003-03/txt/msg00835.txt.bz2 List-Id: Synopsis: bad code generated with optimisation. State-Changed-From-To: open->closed State-Changed-By: ebotcazou State-Changed-When: Fri Mar 14 11:32:55 2003 State-Changed-Why: Not a bug. On x86, when optimizing, floating point values may be kept in FP registers when doing comparison with others stored in memory. Now x86 FP registers have extra-precision over a 'double', which may invalid an equality comparison. Compile your code with '-ffloat-store' if it relies on exact IEEE floating-point semantics. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10078