public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: haochen.jiang@intel.com, gcc-patches@gcc.gnu.org,
	gcc-regression@gcc.gnu.org, richard.sandiford@arm.com
Subject: [r13-2288 Regression] FAIL: gcc.dg/vect/bb-slp-pr54400.c scan-tree-dump-not slp2 " = VEC_PERM_EXPR" on Linux/x86_64
Date: Thu, 01 Sep 2022 09:39:37 +0800	[thread overview]
Message-ID: <202209010139.2811dbu03591674@shliclel314.sh.intel.com> (raw)

On Linux/x86_64,

61c4c989034548f481d1f10198447be27fb9a55f is the first bad commit
commit 61c4c989034548f481d1f10198447be27fb9a55f
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Tue Aug 30 15:43:47 2022 +0100

    Extend SLP permutation optimisations

caused

FAIL: gcc.dg/vect/bb-slp-pr54400.c -flto -ffat-lto-objects  scan-tree-dump-not slp2 " = VEC_PERM_EXPR"
FAIL: gcc.dg/vect/bb-slp-pr54400.c scan-tree-dump-not slp2 " = VEC_PERM_EXPR"

with GCC configured with

../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-2288/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=gcc.dg/vect/bb-slp-pr54400.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/bb-slp-pr54400.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/bb-slp-pr54400.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="vect.exp=gcc.dg/vect/bb-slp-pr54400.c --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)

                 reply	other threads:[~2022-09-01  1:39 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=202209010139.2811dbu03591674@shliclel314.sh.intel.com \
    --to=haochenj@ecsmtp.sh.intel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=haochen.jiang@intel.com \
    --cc=richard.sandiford@arm.com \
    /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).