public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105297] [12 Regression] new modules 'xtreme' test cases FAILs Date: Wed, 20 Apr 2022 14:29:06 +0000 [thread overview] Message-ID: <bug-105297-4-sXEGe8SVN5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105297-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105297 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |redi at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- If we want a quick work-around, I think: --- libstdc++-v3/include/std/charconv.jj 2022-04-19 07:20:56.772166410 +0200 +++ libstdc++-v3/include/std/charconv 2022-04-20 16:27:47.971314921 +0200 @@ -407,6 +407,10 @@ namespace __detail return true; } + struct __from_chars_alnum_to_val_table_type { + unsigned char __data[1u << __CHAR_BIT__] = {}; + }; + // Construct and return a lookup table that maps 0-9, A-Z and a-z to their // corresponding base-36 value and maps all other characters to 127. constexpr auto @@ -420,7 +424,7 @@ namespace __detail = { 'A', 'B', 'C', 'D', 'E', 'F', 'G', 'H', 'I', 'J', 'K', 'L', 'M', 'N', 'O', 'P', 'Q', 'R', 'S', 'T', 'U', 'V', 'W', 'X', 'Y', 'Z' }; - struct { unsigned char __data[1u << __CHAR_BIT__] = {}; } __table; + struct __from_chars_alnum_to_val_table_type __table; for (auto& __entry : __table.__data) __entry = 127; for (int __i = 0; __i < 10; ++__i) or so would do it.
next prev parent reply other threads:[~2022-04-20 14:29 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 20:21 [Bug c++/105297] New: " iains at gcc dot gnu.org 2022-04-16 20:22 ` [Bug c++/105297] " iains at gcc dot gnu.org 2022-04-20 13:53 ` jakub at gcc dot gnu.org 2022-04-20 13:59 ` jakub at gcc dot gnu.org 2022-04-20 14:23 ` jakub at gcc dot gnu.org 2022-04-20 14:29 ` jakub at gcc dot gnu.org [this message] 2022-04-20 14:31 ` hp at gcc dot gnu.org 2022-04-20 16:01 ` redi at gcc dot gnu.org 2022-04-20 16:14 ` ppalka at gcc dot gnu.org 2022-04-20 16:18 ` ppalka at gcc dot gnu.org 2022-04-20 17:17 ` jakub at gcc dot gnu.org 2022-04-20 17:59 ` ppalka at gcc dot gnu.org 2022-04-21 9:25 ` guojiufu at gcc dot gnu.org 2022-04-21 12:35 ` cvs-commit at gcc dot gnu.org 2022-04-21 13:13 ` ppalka at gcc dot gnu.org 2022-04-21 13:14 ` ppalka at gcc dot gnu.org 2022-04-22 5:53 ` guojiufu 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-105297-4-sXEGe8SVN5@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: 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).