https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82103
--- Comment #6 from Jeffrey A. Law ---
It should. It may not though because one the n != 0 test is removed, the
resulting range of N is probably VR_VARYING rather than ~[0,0] at the call to
memset.
The former signifies we know nothing about the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82103
--- Comment #5 from Arnd Bergmann ---
In that case, shouldn't we also warn if the conditional function call in front
of it wasn't there, or without the '__n != 0' check?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82103
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82103
--- Comment #3 from Marc Glisse ---
This warning is "less wrong" than the other related ones. If frame_size is 0,
this does call memset(,,-1). And there is an explicit test for frame_size == 0
in the function, which makes it look like 0 is not su
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82103
Martin Sebor changed:
What|Removed |Added
Component|rtl-optimization|tree-optimization
See Also|
