From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: haochen.jiang@intel.com, gcc-patches@gcc.gnu.org,
gcc-regression@gcc.gnu.org, mliska@suse.cz
Subject: [r13-3463 Regression] FAIL: gcc.target/i386/builtin_target.c (test for excess errors) on Linux/x86_64
Date: Tue, 25 Oct 2022 11:39:53 +0800 [thread overview]
Message-ID: <202210250339.29P3drd42145348@shliclel314.sh.intel.com> (raw)
On Linux/x86_64,
f751bf4c5d1aaa1aacfcbdec62881c5ea1175dfb is the first bad commit
commit f751bf4c5d1aaa1aacfcbdec62881c5ea1175dfb
Author: Martin Liska <mliska@suse.cz>
Date: Mon Oct 24 15:34:39 2022 +0200
x86: fix VENDOR_MAX enum value
caused
FAIL: gcc.target/i386/builtin_target.c (test for excess errors)
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r13-3463/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/builtin_target.c --target_board='unix{-m32}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/builtin_target.c --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/builtin_target.c --target_board='unix{-m64}'"
$ cd {build_dir}/gcc && make check RUNTESTFLAGS="i386.exp=gcc.target/i386/builtin_target.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-10-25 3:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 3:39 haochen.jiang [this message]
2022-10-25 4:23 ` [PATCH][pushed] i386: fix pedantic warning Martin Liška
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=202210250339.29P3drd42145348@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=mliska@suse.cz \
/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).