Re: [r16-372 Regression] FAIL: gfortran.dg/specifics_1.f90 -O3 -g execution test on Linux/x86_64
Andrew Pinski via Gcc-regression <[email protected]>
| Newsgroups | gmane.comp.gcc.regression,gmane.comp.gcc.patches |
|---|---|
| Message-ID | <CA+=Sn1m_C=cS5c0REh1HwxE8qBrYaFxZ7B3rFATGKQ8_6nVH8Q@mail.gmail.com> |
On Sun, May 18, 2025 at 11:19 PM haochen.jiang <[email protected]> wrote: > > On Linux/x86_64, > > 064cac730f88dc71c6da578f9ae5b8e092ab6cd4 is the first bad commit > commit 064cac730f88dc71c6da578f9ae5b8e092ab6cd4 > Author: Jan Hubicka <[email protected]> > Date: Sun May 4 10:52:35 2025 +0200 > > Improve maybe_hot handling in inliner heuristics > > caused > > FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "Alignment of access forced using peeling" 1 > FAIL: gcc.dg/tree-ssa/gen-vect-28.c scan-tree-dump-times vect "vectorized 1 loops" 1 > FAIL: gcc.dg/tree-ssa/pr81627.c scan-tree-dump-times pcom "Store-stores chain" 1 This is just an extra inlining which causes pcom to happen twice now. Will look into fix that this coming week. > FAIL: gcc.target/i386/avx512vl-vpmovuswb-2.c (test for excess errors) > FAIL: gcc.target/i386/avx512vl-vpmovwb-2.c (test for excess errors) > FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C -O2 execution test > FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test > FAIL: g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C -O3 -g execution test > FAIL: g++.dg/coroutines/torture/func-params-07.C -O2 execution test > FAIL: g++.dg/coroutines/torture/func-params-07.C -O3 -g execution test > FAIL: g++.dg/coroutines/torture/pr103953.C -O2 execution test > FAIL: g++.dg/coroutines/torture/pr103953.C -O3 -g execution test The coroutines failures might be a front-end issue or a testcase issue dealing with operator new. > FAIL: g++.dg/vect/pr64410.cc -std=c++17 scan-tree-dump vect "vectorized 1 loops in function" > FAIL: g++.dg/vect/pr64410.cc -std=c++26 scan-tree-dump vect "vectorized 1 loops in function" > FAIL: gfortran.dg/guality/arg1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions line 14 a(10) == 10 > FAIL: gfortran.dg/specifics_1.f90 -O2 execution test > FAIL: gfortran.dg/specifics_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test > FAIL: gfortran.dg/specifics_1.f90 -O3 -g execution test The specifics_1 failure is a front-end bug which is being fixed: https://gcc.gnu.org/pipermail/gcc-patches/2025-May/684016.html . > > with GCC configured with > > ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r16-372/usr --enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --with-fpmath=sse --enable-languages=c,c++,fortran --enable-cet --without-isl --enable-libmpx x86_64-linux --disable-bootstrap > > To reproduce: > > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/gen-vect-28.c --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/gen-vect-28.c --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/pr81627.c --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovuswb-2.c --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/avx512vl-vpmovwb-2.c --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/exceptions-test-01-n4849-a.C --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/func-params-07.C --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/func-params-07.C --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/func-params-07.C --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/func-params-07.C --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/pr103953.C --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/pr103953.C --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/pr103953.C --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="coro-torture.exp=g++.dg/coroutines/torture/pr103953.C --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=g++.dg/vect/pr64410.cc --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=g++.dg/vect/pr64410.cc --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=g++.dg/vect/pr64410.cc --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=g++.dg/vect/pr64410.cc --target_board='unix{-m64\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="guality.exp=gfortran.dg/guality/arg1.f90 --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/specifics_1.f90 --target_board='unix{-m32}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/specifics_1.f90 --target_board='unix{-m32\ -march=cascadelake}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/specifics_1.f90 --target_board='unix{-m64}'" > $ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/specifics_1.f90 --target_board='unix{-m64\ -march=cascadelake}'" > > (Please do not reply to this email, for question about this report, contact me at haochen dot jiang at intel.com.) > (If you met problems with cascadelake related, disabling AVX512F in command line might save that.) > (However, please make sure that there is no potential problems with AVX512.)