From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: haochen.jiang@intel.com, gcc-patches@gcc.gnu.org,
gcc-regression@gcc.gnu.org, jakub@redhat.com
Subject: [r13-4268 Regression] FAIL: gcc.dg/pr107127.c (test for excess errors) on Linux/x86_64
Date: Thu, 24 Nov 2022 09:37:54 +0800 [thread overview]
Message-ID: <202211240137.2AO1bs8L789884@shliclel314.sh.intel.com> (raw)
On Linux/x86_64,
8a0fce6a51915c29584427fd376b40073c328090 is the first bad commit
commit 8a0fce6a51915c29584427fd376b40073c328090
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Nov 23 19:09:31 2022 +0100
c: Fix compile time hog in c_genericize [PR107127]
caused
FAIL: gcc.dg/pr107127.c (test for excess errors)
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-4268/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="dg.exp=gcc.dg/pr107127.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr107127.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr107127.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="dg.exp=gcc.dg/pr107127.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)
next reply other threads:[~2022-11-24 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 1:37 haochen.jiang [this message]
2022-11-24 9:37 ` [committed] testsuite: Fix up broken testcase [PR107127] Jakub Jelinek
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=202211240137.2AO1bs8L789884@shliclel314.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=jakub@redhat.com \
/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).