public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103687] [12 regression] several time/date failures after r12-5898
Date: Tue, 14 Dec 2021 23:37:26 +0000 [thread overview]
Message-ID: <bug-103687-4-S0Rgn34HJc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103687-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103687
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:9a4b4514bde2fe2f287f6549ef51326fb8918008
commit r12-5980-g9a4b4514bde2fe2f287f6549ef51326fb8918008
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Dec 14 22:14:48 2021 +0000
libstdc++: Support old and new T_FMT for en_HK locale [PR103687]
This checks whether the locale data for en_HK includes %p and adjusts
the string being tested accordingly. To account for Jakub's fix to make
%I parse "12" as 0 instead of 12, we need to change the expected value
for the case where the locale format doesn't include %p. Also change the
time from 12:00:00 to 12:02:01 so we can tell if the minutes and seconds
get mixed up.
libstdc++-v3/ChangeLog:
PR libstdc++/103687
* testsuite/22_locale/time_get/get_date/wchar_t/4.cc: Restore
original locale before returning.
* testsuite/22_locale/time_get/get_time/char/2.cc: Check for %p
in locale's T_FMT and adjust accordingly.
* testsuite/22_locale/time_get/get_time/wchar_t/2.cc: Likewise.
next prev parent reply other threads:[~2021-12-14 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 15:26 [Bug libstdc++/103687] New: " seurer at gcc dot gnu.org
2021-12-13 15:28 ` [Bug libstdc++/103687] " seurer at gcc dot gnu.org
2021-12-13 17:06 ` redi at gcc dot gnu.org
2021-12-13 17:12 ` seurer at gcc dot gnu.org
2021-12-13 22:10 ` jakub at gcc dot gnu.org
2021-12-14 11:41 ` jakub at gcc dot gnu.org
2021-12-14 11:47 ` jakub at gcc dot gnu.org
2021-12-14 13:27 ` jakub at gcc dot gnu.org
2021-12-14 14:44 ` redi at gcc dot gnu.org
2021-12-14 14:46 ` redi at gcc dot gnu.org
2021-12-14 14:48 ` redi at gcc dot gnu.org
2021-12-14 16:15 ` redi at gcc dot gnu.org
2021-12-14 23:37 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-14 23:39 ` redi at gcc dot gnu.org
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=bug-103687-4-S0Rgn34HJc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).