[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #6 from David Binderman --- I am trying a bisect with git hash b4fca4fc70dc76cf.

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #5 from David Binderman --- I have reduced one of the test cases downto this code: float val1f[][2], val2f[][2], chkf[][2]; foof_i; foof() { int j; foof_i = 0; for (; foof_i < 8; foof_i++) { float tmp = val1f[foof_i][j] *

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #4 from David Binderman --- A third: ./gcc.target/i386/pr61403.c ==749959== Conditional jump or move depends on uninitialised value(s) ==749959==at 0x11DFAE7: bitmap_set_bit (sbitmap.h:137) ==749959==by 0x11DFAE7:

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #3 from David Binderman --- Another test case: ./gcc.target/i386/pr53366-2.c ==41== Conditional jump or move depends on uninitialised value(s) ==41==at 0x11DFAE7: bitmap_set_bit (sbitmap.h:137) ==41==by

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #2 from David Binderman --- git blame says dc95e1e970 (Hongyu Wang 2022-01-17 13:01:51 +0800 8292)if (!bitmap_set_bit (seen, sel[i].to_constant ()))

[Bug c/107734] valgrind error for gcc/testsuite/cc.target/i386/pr46051.c

2022-11-17 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107734 --- Comment #1 from David Binderman --- The valgrind problem doesn't seem to occur with git hash 05432288d4e56055, dated 20221113, so the bug is recent. I used git hash 2b2f2ee49a33419f for today's build.