From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-regression@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [r14-6468 Regression] FAIL: std/time/year/io.cc -std=gnu++26 execution test on Linux/x86_64
Date: Wed, 13 Dec 2023 17:06:15 +0000 [thread overview]
Message-ID: <CACb0b4nPKg=GfZJxhttZ2QTY=1ZpvW1ZrKLBfhy6mS1OUZaeOw@mail.gmail.com> (raw)
In-Reply-To: <202312131048.3BDAm0Qc1482962@shliclel4214.sh.intel.com>
On Wed, 13 Dec 2023 at 10:51, haochen.jiang
<haochenj@ecsmtp.sh.intel.com> wrote:
>
> On Linux/x86_64,
>
> a01462ae8bafa86e7df47a252917ba6899d587cf is the first bad commit
> commit a01462ae8bafa86e7df47a252917ba6899d587cf
> Author: Jonathan Wakely <jwakely@redhat.com>
> Date: Mon Dec 11 15:33:59 2023 +0000
>
> libstdc++: Fix std::format output of %C for negative years
>
> caused
>
> FAIL: std/time/year/io.cc -std=gnu++20 execution test
> FAIL: std/time/year/io.cc -std=gnu++26 execution test
>
> with GCC configured with
>
> ../../gcc/configure --prefix=/export/users/haochenj/src/gcc-bisect/master/master/r14-6468/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/time/year/io.cc --target_board='unix{-m32}'"
> $ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/time/year/io.cc --target_board='unix{-m32\ -march=cascadelake}'"
> $ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/time/year/io.cc --target_board='unix{-m64}'"
> $ cd {build_dir}/x86_64-linux/libstdc++-v3/testsuite && make check RUNTESTFLAGS="conformance.exp=std/time/year/io.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.)
> (If you met problems with cascadelake related, disabling AVX512F in command line might save that.)
> (However, please make sure that there is no potential problems with AVX512.)
Thanks, fixed at r14-6493-gad537ccd525fd3
prev parent reply other threads:[~2023-12-13 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 10:48 haochen.jiang
2023-12-13 17:06 ` Jonathan Wakely [this message]
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='CACb0b4nPKg=GfZJxhttZ2QTY=1ZpvW1ZrKLBfhy6mS1OUZaeOw@mail.gmail.com' \
--to=jwakely@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).