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>
Subject: [r13-5092 Regression] FAIL: gcc.dg/tree-ssa/ssa-dse-46.c (test for excess errors) on Linux/x86_64
Date: Wed, 11 Jan 2023 02:40:30 +0000 [thread overview]
Message-ID: <SA1PR11MB59462A43B3461FBA9EAF38B8ECFC9@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Hi all,
This is the bisect result for the latest regression which fail to send to mailing list.
It seems that the mail command in s-nail went down after my machine got upgraded, still investigating why.
On Linux/x86_64,
4e0b504f26f78ff02e80ad98ebbf8ded3aa6ffa1 is the first bad commit
commit 4e0b504f26f78ff02e80ad98ebbf8ded3aa6ffa1
Author: Richard Biener <rguenther@suse.de<mailto:rguenther@suse.de>>
Date: Tue Jan 10 13:48:51 2023 +0100
tree-optimization/106293 - missed DSE with virtual LC PHI
caused
FAIL: gcc.dg/tree-ssa/ssa-dse-46.c (test for excess errors)
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-5092/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="tree-ssa.exp=gcc.dg/tree-ssa/ssa-dse-46.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="tree-ssa.exp=gcc.dg/tree-ssa/ssa-dse-46.c --target_board='unix{-m32\ -march=cascadelake}'"
BRs,
Haochen
reply other threads:[~2023-01-11 2:40 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=SA1PR11MB59462A43B3461FBA9EAF38B8ECFC9@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).