https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93388
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Binderman from comment #4)
> I tried out -fanalyzer with all the C code under gcc/testsuite.
>
> There are 35368 C source code files. 234 crashes so far.
>
> Here are the first ten:
Thanks.
These look like duplicates: I tried to repeat this with current master by
adding -fanalyzer to gcc.dg/dg.exp's DEFAULT_CFLAGS, and I didn't see any
crashes with:
make check-gcc RUNTESTFLAGS="-v -v --target_board=unix\{-m32,-m64\} dg.exp=*"
=== gcc Summary ===
# of expected passes 54990
# of unexpected failures 9
# of expected failures 654
# of unsupported tests 328
The unexpected failures were warnings from the analyzer, which appear valid:
gcc.dg/20000111-1.c (test for excess errors)
gcc.dg/20000111-1.c:9:10: warning: use of uninitialized value 'p' [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
(warning looks valid)
gcc.dg/20000906-1.c (test for excess errors)
gcc.dg/20000906-1.c:11:25: warning: use of uninitialized value 'lp.v'
[CWE-457] [-Wanalyzer-use-of-uninitialized-value]
(not sure about this one)
gcc.dg/loop-1.c (test for excess errors)
gcc.dg/loop-1.c:17:17: warning: use of uninitialized value 'prod' [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
(warning looks valid)
gcc.dg/pr71558.c (test for excess errors)
gcc.dg/pr71558.c:16:10: warning: use of possibly-NULL 'c' where non-null
expected [CWE-690] [-Wanalyzer-possible-null-argument]
(warning looks valid)
gcc.dg/pr93661.c (test for warnings, line 7)
looks like a pre-existing 32-bit vs 64-bit issue with the test
