[Bug analyzer/103658] missing -Wanalyzer-use-of-uninitialized-value at -O1 and below for an array access

2022-02-09 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103658 David Malcolm changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED

[Bug analyzer/103658] missing -Wanalyzer-use-of-uninitialized-value at -O1 and below for an array access

2022-02-09 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103658 --- Comment #2 from David Malcolm --- Note that with -fno-analyzer-state-merge, -fanalyzer warns without optimization and shows the conditionals you hoped to see: ./xgcc -B. -S -fanalyzer /tmp/foo.c -fno-analyzer-state-merge /tmp/foo.c: In

[Bug analyzer/103658] missing -Wanalyzer-use-of-uninitialized-value at -O1 and below for an array access

2021-12-10 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103658 --- Comment #1 from Martin Sebor --- Actually, what I was really after is trying to see if the analyzer would print the conditionals involved in the subscript expressions. But in the simple test case in comment #0 there are no conditionals.