public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [r11-4427 Regression] FAIL: gfortran.dg/vect/pr83232.f90   -O scan-tree-dump-times slp1 "vectorizing stmts using SLP" 3 on Linux/x86_64
@ 2020-10-27 22:13 sunil.k.pandey
  2020-10-28  8:12 ` Richard Biener
  0 siblings, 1 reply; 2+ messages in thread
From: sunil.k.pandey @ 2020-10-27 22:13 UTC (permalink / raw)
  To: gcc-patches, gcc-regression, rguenther

On Linux/x86_64,

5af1e827bbb624eb28f80d2c5e0da46185af3708 is the first bad commit
commit 5af1e827bbb624eb28f80d2c5e0da46185af3708
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Oct 27 11:03:27 2020 +0100

    Avoid uniform lane BB vectorization

caused

FAIL: gfortran.dg/vect/pr83232.f90   -O   scan-tree-dump-times slp1 "vectorizing stmts using SLP" 3

with GCC configured with

../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r11-4427/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="vect.exp=gfortran.dg/vect/pr83232.f90 --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gfortran.dg/vect/pr83232.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)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [r11-4427 Regression] FAIL: gfortran.dg/vect/pr83232.f90 -O scan-tree-dump-times slp1 "vectorizing stmts using SLP" 3 on Linux/x86_64
  2020-10-27 22:13 [r11-4427 Regression] FAIL: gfortran.dg/vect/pr83232.f90 -O scan-tree-dump-times slp1 "vectorizing stmts using SLP" 3 on Linux/x86_64 sunil.k.pandey
@ 2020-10-28  8:12 ` Richard Biener
  0 siblings, 0 replies; 2+ messages in thread
From: Richard Biener @ 2020-10-28  8:12 UTC (permalink / raw)
  To: sunil.k.pandey; +Cc: gcc-patches, gcc-regression

On Tue, 27 Oct 2020, sunil.k.pandey wrote:

> On Linux/x86_64,
> 
> 5af1e827bbb624eb28f80d2c5e0da46185af3708 is the first bad commit
> commit 5af1e827bbb624eb28f80d2c5e0da46185af3708
> Author: Richard Biener <rguenther@suse.de>
> Date:   Tue Oct 27 11:03:27 2020 +0100
> 
>     Avoid uniform lane BB vectorization
> 
> caused
> 
> FAIL: gfortran.dg/vect/pr83232.f90   -O   scan-tree-dump-times slp1 "vectorizing stmts using SLP" 3
> 
> with GCC configured with
> 
> ../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r11-4427/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="vect.exp=gfortran.dg/vect/pr83232.f90 --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gfortran.dg/vect/pr83232.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)

So the testcase is now improved with AVX but the dump scanning doesn't
match the need to split the vectorization at (1) into a AVX and SSE
part.  There's no suitable target selector yet, the vect_sizes_32B_16B
one is an exact match and doesn't fit.  I filed PR97611 for the
testsuite harness issue.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-10-28  8:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-27 22:13 [r11-4427 Regression] FAIL: gfortran.dg/vect/pr83232.f90 -O scan-tree-dump-times slp1 "vectorizing stmts using SLP" 3 on Linux/x86_64 sunil.k.pandey
2020-10-28  8:12 ` Richard Biener

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).