[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-11-23 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #10 from Vincent Lefèvre --- A similar bug (all uses of the variable are under some condition) with a simpler testcase I've just reported: PR107839.

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-10-17 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Richard Biener changed: What|Removed |Added Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot gnu.org

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #9 from Richard Biener --- This is another example where when doing PHI chaining, we fail to consider the use predicate of the PHI operand in the final PHI which has now no further guard before the use.

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #8 from Richard Biener --- The following variant warns with all GCC releases I tested (and -fno-ivopts fixes it), not exposing a mitigating jump threading opportunity: int *e; int f1 (void); void f2 (int); long f3 (void *, long,

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-09-06 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #7 from Richard Biener --- This should now be fixed up to the confusion due to IVOPTs. As said the narrowing is problematic here :/

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-08-31 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Richard Biener changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-08-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Richard Biener changed: What|Removed |Added Target Milestone|12.2|12.3 --- Comment #5 from Richard

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-07-25 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Richard Biener changed: What|Removed |Added Priority|P3 |P2

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-07-04 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Martin Liška changed: What|Removed |Added Keywords|needs-bisection | CC|

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-06-30 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Andrew Pinski changed: What|Removed |Added Keywords||needs-bisection --- Comment #3 from

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-06-30 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2022-07-01 Keywords|

[Bug tree-optimization/106155] [12/13 Regression] spurious "may be used uninitialized" warning

2022-06-30 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106155 --- Comment #1 from Vincent Lefèvre --- I detected the issue on tests/tfpif.c with the upgrade of Debian's package gcc-snapshot from 1:20220126-1 to 1:20220630-1 (it doesn't occur on tests/tfpif.c with gcc-snapshot 1:20220126-1). However, the