https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
--- Comment #1 from Andrew Pinski ---
So there might be some jump threading going on which is causing this issue.
There might already be a bug about that case too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2020-04-06
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
--- Comment #3 from Richard Biener ---
Created attachment 48213
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48213&action=edit
incomplete patch
In case anybody is interested to complete it ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
--- Comment #4 from Richard Biener ---
As a workaround you can use -ffinite-math-only -fno-signed-zeros if that is
applicable to the rest of your application.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
--- Comment #5 from Hadrien Grasland ---
Thanks for the clarifications! We could probably live with -fno-signed-zeros,
but I think -ffinite-math-only would be too much as an application-wide flag,
as I've spotted several occurences of the "do the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-* i?86-*-*
--- Comment #6 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94497
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #7 from Andrew P
