https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
--- Comment #10 from Eric Gallager ---
This might be material for David Malcolm's new static analyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
Konstantin Kharlamov changed:
What|Removed |Added
CC||Hi-Angel at yandex dot ru
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
Eric Gallager changed:
What|Removed |Added
Keywords||patch
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
--- Comment #6 from Manuel López-Ibáñez ---
(In reply to Manuel López-Ibáñez from comment #5)
> (In reply to Andrew Pinski from comment #2)
> > This needs data flow to see if b usage cross over the clobber or not.
>
> I think the simpler case ca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
--- Comment #5 from Manuel López-Ibáñez ---
(In reply to Andrew Pinski from comment #2)
> This needs data flow to see if b usage cross over the clobber or not.
I think the simpler case can be warned in the FE. I cannot imagine a correct
use of a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
--- Comment #4 from Andrew Pinski ---
This also should be detected at runtime with either -fsantizer=undefined or
-fsantizer=address (if it is not, please file another bug for that).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77433
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
