[Bug tree-optimization/82103] spurious stringop-overflow warning

[glisse at gcc dot gnu.org]

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

--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
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 such an absurd value for
frame_size. If we are going to keep the "maybe" variant of this warning at all,
warning for this function makes sense...