https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113251
Ilya Leoshkevich <iii at linux dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iii at linux dot ibm.com
--- Comment #1 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
I can reproduce this manually and will work on a fix.
Surprisingly, this does not show in my test results. I.e.:
$ make check-gcc RUNTESTFLAGS="asan.exp=pr63845.c --debug"
=== gcc Summary ===
# of expected passes 7
$ cat gcc/testsuite/gcc/gcc.sum
PASS: gcc.dg/asan/pr63845.c -O0 (test for excess errors)
PASS: gcc.dg/asan/pr63845.c -O1 (test for excess errors)
PASS: gcc.dg/asan/pr63845.c -O2 (test for excess errors)
PASS: gcc.dg/asan/pr63845.c -O3 -g (test for excess errors)
PASS: gcc.dg/asan/pr63845.c -Os (test for excess errors)
PASS: gcc.dg/asan/pr63845.c -O2 -flto -fno-use-linker-plugin
-flto-partition=none (test for excess errors)
PASS: gcc.dg/asan/pr63845.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (test for excess errors)
But!
$ cat gcc/testsuite/gcc/dbg.log
expect: does "fPIC170653.c:3:13: internal compiler error: Segmentation
fault\r\n" (spawn_id exp7) match regular expression ".+"? (No Gate, RE only)
gate=yes re=yes
compiler exited with status 1
So the problem manifests itself during the test run, but the runner fails to
recognize it for some reason.
