public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Uros Bizjak <uros@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-6589] libstdc++: Fix 22_locale/numpunct/members/char/3.cc execution test Date: Fri, 14 Jan 2022 15:22:08 +0000 (GMT) [thread overview] Message-ID: <20220114152208.3C56E3858D35@sourceware.org> (raw) https://gcc.gnu.org/g:6795e6ae66096d52a62e20ed33a47599233ab3d5 commit r12-6589-g6795e6ae66096d52a62e20ed33a47599233ab3d5 Author: Uros Bizjak <ubizjak@gmail.com> Date: Fri Jan 14 16:21:02 2022 +0100 libstdc++: Fix 22_locale/numpunct/members/char/3.cc execution test The test fails on Fedora 33+ because nl_NL locale got thousands separator defined. Use one of ar_SA, bg_BG, bs_BA, pt_PT or plain C locale instead. 2022-01-14 Uroš Bizjak <ubizjak@gmail.com> libstdc++-v3/ChangeLog: * testsuite/22_locale/numpunct/members/char/3.cc: Require pt_PT locale instead of nl_NL. (test02): Use pt_PT locale instead of nl_NL. Diff: --- libstdc++-v3/testsuite/22_locale/numpunct/members/char/3.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/libstdc++-v3/testsuite/22_locale/numpunct/members/char/3.cc b/libstdc++-v3/testsuite/22_locale/numpunct/members/char/3.cc index 6e4959860cd..19b65d36e88 100644 --- a/libstdc++-v3/testsuite/22_locale/numpunct/members/char/3.cc +++ b/libstdc++-v3/testsuite/22_locale/numpunct/members/char/3.cc @@ -1,4 +1,4 @@ -// { dg-require-namedlocale "nl_NL.ISO8859-15" } +// { dg-require-namedlocale "pt_PT.ISO8859-15" } // 2001-01-24 Benjamin Kosnik <bkoz@redhat.com> @@ -28,8 +28,8 @@ void test02() { using namespace std; - // nl_NL chosen because it has no thousands separator (at this time). - locale loc_it = locale(ISO_8859(15,nl_NL)); + // pt_PT chosen because it has no thousands separator (at this time). + locale loc_it = locale(ISO_8859(15,pt_PT)); const numpunct<char>& nump_it = use_facet<numpunct<char> >(loc_it);
reply other threads:[~2022-01-14 15:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220114152208.3C56E3858D35@sourceware.org \ --to=uros@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).