From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: rguenther@suse.de, gcc-regression@gcc.gnu.org,
gcc-patches@gcc.gnu.org, haochen.jiang@intel.com
Subject: [r14-8206 Regression] FAIL: gfortran.dg/forall_1.f90 -O3 -g (test for excess errors) on Linux/x86_64
Date: Fri, 19 Jan 2024 06:21:34 +0800 [thread overview]
Message-ID: <202401182221.40IMLYwL3938269@shliclel4214.sh.intel.com> (raw)
On Linux/x86_64,
0f38666680d6ad0e40c4a8b6d94b2c93931cdf42 is the first bad commit
commit 0f38666680d6ad0e40c4a8b6d94b2c93931cdf42
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jan 17 13:24:22 2024 +0100
tree-optimization/113374 - early break vect and virtual operands
caused
FAIL: gcc.c-torture/execute/20150611-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/execute/20150611-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: gcc.c-torture/execute/20150611-1.c -O3 -g (internal compiler error: Segmentation fault)
FAIL: gcc.c-torture/execute/20150611-1.c -O3 -g (test for excess errors)
FAIL: gfortran.dg/forall_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error: in add_phi_arg, at tree-phinodes.cc:366)
FAIL: gfortran.dg/forall_1.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: gfortran.dg/forall_1.f90 -O3 -g (internal compiler error: in add_phi_arg, at tree-phinodes.cc:366)
FAIL: gfortran.dg/forall_1.f90 -O3 -g (test for excess errors)
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-8206/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="execute.exp=gcc.c-torture/execute/20150611-1.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="execute.exp=gcc.c-torture/execute/20150611-1.c --target_board='unix{-m64\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/forall_1.f90 --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gfortran.dg/forall_1.f90 --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.)
reply other threads:[~2024-01-18 22:21 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=202401182221.40IMLYwL3938269@shliclel4214.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=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).