From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: "rguenther@suse.de" <rguenther@suse.de>,
"gcc-regression@gcc.gnu.org" <gcc-regression@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Jiang, Haochen" <haochen.jiang@intel.com>
Subject: [r14-3571 Regression] FAIL: gcc.target/i386/pr52252-atom.c scan-assembler palignr on Linux/x86_64
Date: Thu, 31 Aug 2023 01:09:42 +0000 [thread overview]
Message-ID: <SA1PR11MB5946F534CAE2AE47B157CAC3ECE5A@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
In-Reply-To: <202308302136.37ULa8WC1194260@shliclel4214.sh.intel.com>
On Linux/x86_64,
caa7a99a052929d5970677c5b639e1fa5166e334 is the first bad commit
commit caa7a99a052929d5970677c5b639e1fa5166e334
Author: Richard Biener <rguenther@suse.de>
Date: Wed Aug 30 11:57:47 2023 +0200
tree-optimization/111228 - combine two VEC_PERM_EXPRs
caused
FAIL: gcc.target/i386/pr52252-atom.c scan-assembler palignr
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-3571/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="i386.exp=gcc.target/i386/pr52252-atom.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr52252-atom.c --target_board='unix{-m64\ -march=cascadelake}'"
(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.)
next parent reply other threads:[~2023-08-31 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202308302136.37ULa8WC1194260@shliclel4214.sh.intel.com>
2023-08-31 1:09 ` Jiang, Haochen [this message]
2023-08-31 7:09 ` Richard Biener
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=SA1PR11MB5946F534CAE2AE47B157CAC3ECE5A@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@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).