From: "sunil.k.pandey" <skpandey@sc.intel.com>
To: gcc-patches@gcc.gnu.org, gcc-regression@gcc.gnu.org, rguenther@suse.de
Subject: [r11-3204 Regression] FAIL: g++.dg/vect/slp-pr87105.cc -std=c++2a scan-tree-dump-times slp2 "basic block part vectorized" 1 on Linux/x86_64 (-m64 -march=cascadelake)
Date: Tue, 15 Sep 2020 10:44:27 -0700 [thread overview]
Message-ID: <20200915174427.DFDA228FD677@gskx-2.sc.intel.com> (raw)
On Linux/x86_64,
c9de716a59c873859df3b3e1fbb993200fce5a73 is the first bad commit
commit c9de716a59c873859df3b3e1fbb993200fce5a73
Author: Richard Biener <rguenther@suse.de>
Date: Tue Sep 15 14:35:40 2020 +0200
Allow more BB vectorization
caused
FAIL: g++.dg/vect/slp-pr87105.cc -std=c++14 scan-tree-dump slp2 "vect_[^\rm]* = MIN"
FAIL: g++.dg/vect/slp-pr87105.cc -std=c++14 scan-tree-dump-times slp2 "basic block part vectorized" 1
FAIL: g++.dg/vect/slp-pr87105.cc -std=c++17 scan-tree-dump slp2 "vect_[^\rm]* = MIN"
FAIL: g++.dg/vect/slp-pr87105.cc -std=c++17 scan-tree-dump-times slp2 "basic block part vectorized" 1
FAIL: g++.dg/vect/slp-pr87105.cc -std=c++2a scan-tree-dump slp2 "vect_[^\rm]* = MIN"
FAIL: g++.dg/vect/slp-pr87105.cc -std=c++2a scan-tree-dump-times slp2 "basic block part vectorized" 1
with GCC configured with
../../gcc/configure --prefix=/local/skpandey/gccwork/toolwork/gcc-bisect-master/master/r11-3204/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=g++.dg/vect/slp-pr87105.cc --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)
reply other threads:[~2020-09-15 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915174427.DFDA228FD677@gskx-2.sc.intel.com \
--to=skpandey@sc.intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).