https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120747
Filip Kastl <pheeck at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|wrong-code |
--- Comment #6 from Filip Kastl <pheeck at gcc dot gnu.org> ---
Removing the 'wrong-code' keyword. Talked about -Ofast SPEC miscompares with
Richi and now I understand that those aren't really miscompilations: With
-Ofast, FP computations can always have large numerical error.
However, we still want to be able to compile and run SPEC benchmarks with
-Ofast so this is still worth looking into. Perhaps we can change something in
GCC to get rid of this numerical error. Or we find out that it makes more
sense to compile the benchmark with some additional flags or something like
that.
(In reply to Andrew Macleod from comment #5)
> Even knowing which file is miscompiled and what the compile options are would
> be a start.
Not sure how I would figure out which file it is right now. I'll give it some
thought.
