public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
From: "Jiang, Haochen" <haochen.jiang@intel.com>
To: "dmalcolm@redhat.com" <dmalcolm@redhat.com>,
"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: [r13-5244 Regression] FAIL: gcc.dg/analyzer/SARD-tc841-basic-00182-min.c (test for excess errors) on Linux/x86_64
Date: Thu, 19 Jan 2023 01:18:27 +0000 [thread overview]
Message-ID: <SA1PR11MB59460E9AE06569936A268626ECC49@SA1PR11MB5946.namprd11.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
The mail system is still broken on that machine, still sending this manually. Before that mail down, I will keep check the script daily to see if there is new regression.
BTW, since there is a Bugzilla for r13-5202 regression, not resending that report
On Linux/x86_64,
c6a011119bfa038ccbfc9f123ede14a3d6237fab is the first bad commit
commit c6a011119bfa038ccbfc9f123ede14a3d6237fab
Author: David Malcolm dmalcolm@redhat.com<mailto:dmalcolm@redhat.com>
Date: Wed Jan 18 11:41:47 2023 -0500
analyzer: add SARD testsuite 81
caused
FAIL: gcc.dg/analyzer/SARD-tc841-basic-00182-min.c (test for excess errors)
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-5244/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="analyzer.exp=gcc.dg/analyzer/SARD-tc841-basic-00182-min.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/SARD-tc841-basic-00182-min.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/SARD-tc841-basic-00182-min.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/SARD-tc841-basic-00182-min.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:[~2023-01-19 1:18 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=SA1PR11MB59460E9AE06569936A268626ECC49@SA1PR11MB5946.namprd11.prod.outlook.com \
--to=haochen.jiang@intel.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
/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).