[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-06 Thread dimitry--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 --- Comment #3 from Dimitry Andric --- Alright, I can confirm that adding --param=vrp1-mode=vrp makes the warning go away. However, this option is no longer recognized by gcc-14-6924-g00dea7e8c41. I assume the ranger mode is now the default, and

[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-06 Thread dimitry--- via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 Dimitry Andric changed: What|Removed |Added CC||amacleod at redhat dot com --- Comment

[Bug tree-optimization/113239] [13 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 --- Comment #1 from Andrew Pinski --- So I suspect it is either inlining differences due to slightly increased sizes in some cases or jump threading due to the extra check. I highly doubt that patch is underlying cause of the warning ...