This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: optimization/9052: in C code, "if" statement fails to execute if optimized

From: Eric Botcazou <ebotcazou at libertysurf dot fr>
To: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>
Cc: Richard dot Earnshaw at arm dot com,gcc-gnats at gcc dot gnu dot org,gcc-bugs at gcc dot gnu dot org,nobody at gcc dot gnu dot org,phama at webjockey dot net
Date: Thu, 13 Feb 2003 12:49:31 +0100
Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized
References: <200302121624.h1CGO9G31917@pc960.cambridge.arm.com> <200302121754.54649.ebotcazou@libertysurf.fr> <1045069280.756.84.camel@steven>

> How about 8445, 9654?  Those are "bugs" that disappear with
> -ffloat-store, too.  Like I said, I don't know enough about floating
> point numbers...

Toon seems to think that PR fortran/8445 is indeed the same problem. But it's 
up to him to decide whether to close the bug.

PR optimization/9654 is exactly the same problem: using FP registers on x86 
adds extra-precision which can modify comparison results. Nothing can be done 
about that, other than using -ffloat-store which is precisely intended to 
address the issue.

-- 
Eric Botcazou

Follow-Ups:
- Re: optimization/9052: in C code, "if" statement fails to execute if optimized
  - From: Toon Moene

References:
- Re: optimization/9052: in C code, "if" statement fails to execute if optimized
  - From: Richard Earnshaw
- Re: optimization/9052: in C code, "if" statement fails to execute if optimized
  - From: Eric Botcazou
- Re: optimization/9052: in C code, "if" statement fails to execute if optimized
  - From: Steven Bosscher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]