https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96404
--- Comment #14 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #9)
> valgrind says there is use of uninitialized variable:
I picked _gcov.c and minimized it's unstable compilation under cvise. Then
minimized it under presence of warnings related to var-tracking. Here is the
minimized example:
$ cat _gcov.c
int a;
int b(void) {
for (;;)
for (; a;)
for (unsigned c; c < b; c++)
;
}
$ valgrind --trace-children=yes --track-origins=yes --num-callers=50 --quiet
stage3-gcc/xgcc -Bstage3-gcc -O2 -g -o _gcov-s3.S -DL_gcov -S _gcov.c
==913420== Conditional jump or move depends on uninitialised value(s)
==913420== at 0xDBDABB: vt_find_locations() (in
/home/slyfox/tmp/portage/sys-devel/gcc-11.0.0_pre9999/work/build/stage3-gcc/cc1)
...
