https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031
David Binderman <dcb314 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #22 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Jakub Jelinek from comment #20)
> trying to ensure the reduction doesn't introduce uninitialized var uses
> which weren't there before
I was also thinking this myself, so I went back to the original
test case I reported, before any reduction. This is what I found:
$ for i in ~/gcc/results.202205*/bin/gcc; do echo $i; $i -w
-ftrivial-auto-var-init=zero -O2 -fno-strict-aliasing bug892.c && (./a.out 1 |
fgrep g_50); done
/home/dcb36/gcc/results.20220501/bin/gcc
...checksum after hashing g_50 : 646CF84D
/home/dcb36/gcc/results.20220508/bin/gcc
...checksum after hashing g_50 : 646CF84D
/home/dcb36/gcc/results.20220515/bin/gcc
...checksum after hashing g_50 : C21BF3F9
$
So the original bug is still there and my reduction looks invalid ;-|
Snapshots don't exist between 20220508 and 20220515. Is anyone else
able to bisect that range ?
