This is expected. It was failing at all optimization levels except -Os. The
oversight has been fixed :-).
On Thu, Nov 11, 2021, 20:14 sunil.k.pandey <skpan...@sc.intel.com> wrote:
> On Linux/x86_64,
>
> 3e5a19053310ad090b930fbecebceb28bd1b91a4 is the first bad commit
> commit 3e5a19053310ad090b930fbecebceb28bd1b91a4
> Author: Aldy Hernandez <al...@redhat.com>
> Date: Thu Nov 11 11:27:07 2021 +0100
>
> Resolve entry loop condition for the edge remaining in the loop.
>
> caused
>
> FAIL: gfortran.dg/vector_subscript_1.f90 -O1 execution test
> FAIL: gfortran.dg/vector_subscript_1.f90 -O2 execution test
> FAIL: gfortran.dg/vector_subscript_1.f90 -O3 -fomit-frame-pointer
> -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
> FAIL: gfortran.dg/vector_subscript_1.f90 -O3 -g execution test
> FAIL: gfortran.dg/vector_subscript_1.f90 -Os execution test
>
> with GCC configured with
>
> ../../gcc/configure
> --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r12-5150/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="dg.exp=gfortran.dg/vector_subscript_1.f90
> --target_board='unix{-m32}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gfortran.dg/vector_subscript_1.f90
> --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gfortran.dg/vector_subscript_1.f90
> --target_board='unix{-m64}'"
> $ cd {build_dir}/gcc && make check
> RUNTESTFLAGS="dg.exp=gfortran.dg/vector_subscript_1.f90
> --target_board='unix{-m64\ -march=cascadelake}'"
>
> (Please do not reply to this email, for question about this report,
> contact me at skpgkp2 at gmail dot com)
>
>
