[Bug c++/120138] New: (14/15/16) -Wmaybe-uninitialized triggered after specific optimizations

2025-05-06 Thread tcpreimesberger at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120138 Bug ID: 120138 Summary: (14/15/16) -Wmaybe-uninitialized triggered after specific optimizations Product: gcc Version: 16.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/120138] (14/15/16) -Wmaybe-uninitialized triggered after specific optimizations

2025-05-06 Thread tcpreimesberger at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120138 --- Comment #4 from Thor Preimesberger --- FWIW I bisected to commit d45ddc2c04e471d0dcee016b6edacc00b8341b16 - adding this commit and compiling with -O3 causes two additional jumps to be threaded. The gimple stmt _68 = r[1] in transpose_avx5

[Bug tree-optimization/120138] (14/15/16) -Wmaybe-uninitialized triggered after specific optimizations

2025-05-06 Thread tcpreimesberger at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120138 --- Comment #7 from Thor Preimesberger --- (In reply to Andrew Pinski from comment #6) > (In reply to Andrew Pinski from comment #5) > > The code does look like in the case of M being between 0 and 7 will cause > > use of the uninitilized r[1].