public inbox for gcc-regression@sourceware.org
help / color / mirror / Atom feed
* [r13-3463 Regression] FAIL: gcc.target/i386/builtin_target.c (test for excess errors) on Linux/x86_64
@ 2022-10-25 3:39 haochen.jiang
0 siblings, 0 replies; only message in thread
From: haochen.jiang @ 2022-10-25 3:39 UTC (permalink / raw)
To: haochen.jiang, gcc-patches, gcc-regression, mliska
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)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-10-25 3:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-25 3:39 [r13-3463 Regression] FAIL: gcc.target/i386/builtin_target.c (test for excess errors) on Linux/x86_64 haochen.jiang
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).