Heisenbug likely in kernel: GCC tests builtin-fp-int-inexact.c and builtin-fp-int-inexact-c2x.c intermittently fail #7
Description
When bootstrapping and regtesting GCC on Gentoo, the tests builtin-fp-int-inexact.c and builtin-fp-int-inexact-c2x.c intermittently fail.
The log is not very helpful:
PASS: gcc.dg/torture/builtin-fp-int-inexact.c -O3 -g (test for excess errors)
Setting LD_LIBRARY_PATH to :/home/xry111/git-repos/gcc-build/gcc:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/./libatomic/.libs::/home/xry111/git-repos/gcc-build/gcc:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/./libatomic/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libstdc++-v3/src/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libsanitizer/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libvtv/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libssp/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libgomp/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libitm/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libatomic/.libs:/home/xry111/git-repos/gcc-build/./gcc:/home/xry111/git-repos/gcc-build/./prev-gcc:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libstdc++-v3/src/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libsanitizer/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libvtv/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libssp/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libgomp/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libitm/.libs:/home/xry111/git-repos/gcc-build/loongarch64-unknown-linux-gnu/libatomic/.libs:/home/xry111/git-repos/gcc-build/./gcc:/home/xry111/git-repos/gcc-build/./prev-gcc
Execution timeout is: 300
spawn [open ...]
FAIL: gcc.dg/torture/builtin-fp-int-inexact.c -O3 -g execution test
I don't believe this is a GCC bug (with 99% confidence), so creating an issue here instead of via GCC Bugzilla.