This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/9052: in C code, "if" statement fails to execute if optimized
- From: Eric Botcazou <ebotcazou at libertysurf dot fr>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 12 Feb 2003 16:56:00 -0000
- Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized
- Reply-to: Eric Botcazou <ebotcazou at libertysurf dot fr>
The following reply was made to PR optimization/9052; it has been noted by GNATS.
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Richard.Earnshaw@arm.com
Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>,
gcc-gnats@gcc.gnu.org,
gcc-bugs@gcc.gnu.org,
nobody@gcc.gnu.org,
phama@webjockey.net
Subject: Re: optimization/9052: in C code, "if" statement fails to execute if optimized
Date: Wed, 12 Feb 2003 17:55:22 +0100
> Adding -ffloat-store will probably also make the "misbehaviour" go away.
It does.
> GCC is almost certainly using the register result from the current
> iteration to compare with the memory result from an earlier iteration.
> Since the register result has excess precision the compare for equality
> fails. That's not a bug, it's just the FP works on the X86.
>
> So in summary, almost certainly "not a bug".
I fully concur. I think the PR can be closed.
--
Eric Botcazou