https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113009
--- Comment #3 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Edwin Lu from comment #2)
> Re-bisected to r14-6197-g2e7abd09621
>
> Full steps to reproduce:
> mkdir dump1
> ./build-gcc-linux-stage2/gcc/xgcc -B./build-gcc-linux-stage2/gcc/
> -march=rv64gcv -mabi=lp64d -mcmodel=medlow -fdiagnostics-plain-output -w
> -O3 -g -dumpbase dump1/dump-noaddr.c -DMASK=1 -x c --param
> ggc-min-heapsize=1 -fdump-ipa-all -fdump-rtl-all -fdump-tree-all
> -fdump-noaddr -gno-record-gcc-switches -c -o
> ./build-gcc-linux-stage2/gcc/testsuite/gcc/dump-noaddr.o
> ../gcc/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.c
> mv dump1 dump1-comp
> mkdir dump1
> for i in {1..100}; do
> ./build-gcc-linux-stage2/gcc/xgcc -B./build-gcc-linux-stage2/gcc/
> -march=rv64gcv -mabi=lp64d -mcmodel=medlow -fdiagnostics-plain-output -w
> -O3 -g -dumpbase dump1/dump-noaddr.c -DMASK=1 -x c --param
> ggc-min-heapsize=1 -fdump-ipa-all -fdump-rtl-all -fdump-tree-all
> -fdump-noaddr -gno-record-gcc-switches -c -o
> ./build-gcc-linux-stage2/gcc/testsuite/gcc/dump-noaddr.o
> ../gcc/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.c && diff -d
> dump1/dump-noaddr.c.*r.avlprop ./dump1-comp/dump-noaddr.c.*r.avlprop;
> done
>
> may take around 2-3 min for the diff output to start appearing depending on
> whether the expected output is saved into dump-comp or not
Thanks for reporting it. I will take a look at it.
That commit is to fix ICE and execution issues (real bugs).
We are busy with fixing real bugs (ICE and execution FAILs) on full coverage
testing.
Dump FAILs are bogus FAILs, it's low priority for now.
