[Bug tree-optimization/115125] [-Wstringop-overflow=] with O2/O3 - false positive?

[sjames at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #4 from Sam James  ---
I see -Warray-bounds with 12/13/14/15. I don't see -Wstringop-overflow at all
here.

[Bug tree-optimization/115125] [-Wstringop-overflow=] with O2/O3 - false positive?

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  changed:

   What|Removed |Added

  Known to work||15.0
   Keywords||needs-bisection

--- Comment #3 from Andrew Pinski  ---
Seems to be fixed on the trunk ...

[Bug tree-optimization/115125] [-Wstringop-overflow=] with O2/O3 - false positive?

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #2 from Andrew Pinski  ---
(In reply to Nikolai Ivanenko from comment #1)
> Forgot to mention that the the code commented out in main compiles without
> warnings.

That is just due to inlining differences. Afterwards if you rename main to f
and change the return type to void, you get back the warnings. GCC is less
agressive at inlining into main (unless the call is inside a loop) as GCC knows
that function call is only happens once.