https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97185
--- Comment #3 from Siddhesh Poyarekar ---
(In reply to Martin Sebor from comment #2)
> There's a heuristic for ranges of allocation sizes to exclude zero
> (size_range_flags) that comes into play here. The actual range isn't
> "impossible" in t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97185
--- Comment #2 from Martin Sebor ---
There's a heuristic for ranges of allocation sizes to exclude zero
(size_range_flags) that comes into play here. The actual range isn't
"impossible" in the sense it's necessarily invalid. It just means the s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97185
--- Comment #1 from Siddhesh Poyarekar ---
While the missed optimization ought to be fixed, what's the value of
-Wstringop-* warning on an impossible range, i.e. when low > high? Shouldn't
it just bail out silently if it detects an impossible ra
