[Bug middle-end/110556] Floating point exception with specific optimizations

pinskia at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Thu Jul 6 01:38:55 GMT 2023


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110556

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to CTC from comment #6)
> (In reply to Andrew Pinski from comment #4)
> > Reducing this but it is taking a little longer as I get to the case where we
> > get undefined code on accident so I need to test it using
> > -fsanitize=undefined,address also.
> 
> For the unreduced program and optimizations, I test it with
> -fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations and
> -fsanitize=undefined. Both of them got floating point exception too.
> 
> I reduced the program with -fsanitize=undefined. The result doesn't get
> floating point exception. But its return value is not 0.

That is still undefined code ... as the return value of the app is not
specified in the source.


More information about the Gcc-bugs mailing list