From: "haochen.jiang" <haochenj@ecsmtp.sh.intel.com>
To: jason@redhat.com, gcc-regression@gcc.gnu.org,
gcc-patches@gcc.gnu.org, haochen.jiang@intel.com
Subject: [r14-159 Regression] FAIL: std/ranges/iota/max_size_type.cc execution test on Linux/x86_64
Date: Sat, 22 Apr 2023 11:30:24 +0800 [thread overview]
Message-ID: <202304220330.33M3UOTu3169661@shliclel4214.sh.intel.com> (raw)
On Linux/x86_64,
03cebd304955a6b9c5607e09312d77f1307cc98e is the first bad commit
commit 03cebd304955a6b9c5607e09312d77f1307cc98e
Author: Jason Merrill <jason@redhat.com>
Date: Tue Apr 18 21:32:07 2023 -0400
c++: fix 'unsigned typedef-name' extension [PR108099]
caused
FAIL: std/ranges/iota/max_size_type.cc execution test
with GCC configured with
../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-159/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}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/ranges/iota/max_size_type.cc --target_board='unix{-m32}'"
$ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/ranges/iota/max_size_type.cc --target_board='unix{-m32\ -march=cascadelake}'"
$ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/ranges/iota/max_size_type.cc --target_board='unix{-m64}'"
$ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/ranges/iota/max_size_type.cc --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:[~2023-04-22 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 3:30 haochen.jiang [this message]
2023-04-22 7:44 ` Jakub Jelinek
2023-04-22 23:26 ` Jonathan Wakely
2023-04-24 16:27 ` Patrick Palka
2023-04-24 16:30 ` Jonathan Wakely
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=202304220330.33M3UOTu3169661@shliclel4214.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=jason@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).