* [r14-2946 Regression] FAIL: gcc.target/i386/pr87007-5.c scan-assembler-times vxorps[^\n\r]*xmm[0-9] 0 on Linux/x86_64
[not found] <202308150925.37F9PjGX2942974@shliclel4214.sh.intel.com>
@ 2023-08-16 2:58 ` Jiang, Haochen
0 siblings, 0 replies; only message in thread
From: Jiang, Haochen @ 2023-08-16 2:58 UTC (permalink / raw)
To: rguenther, gcc-regression, gcc-patches, Jiang, Haochen
From: haochen.jiang <haochenj@shliclel4214.sh.intel.com>
Sent: Tuesday, August 15, 2023 5:26 PM
To: rguenther@suse.de; gcc-regression@gcc.gnu.org; gcc-patches@gcc.gnu.org; Jiang, Haochen <haochen.jiang@intel.com>
Subject: [r14-2946 Regression] FAIL: gcc.target/i386/pr87007-5.c scan-assembler-times vxorps[^\n\r]*xmm[0-9] 0 on Linux/x86_64
On Linux/x86_64,
46c8c225455273ce7f7da7cc5707aed54f23e78d is the first bad commit
commit 46c8c225455273ce7f7da7cc5707aed54f23e78d
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jul 26 15:23:45 2023 +0200
Improve sinking with unrelated defs
caused
FAIL: gcc.target/i386/pr87007-5.c scan-assembler-times vxorps[^\n\r]*xmm[0-9] 0
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-2946/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/pr87007-5.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr87007-5.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr87007-5.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/pr87007-5.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.)
(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.)
^ permalink raw reply [flat|nested] only message in thread