public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r13-3325] libstdc++: Fix value of __cpp_lib_constexpr_charconv Date: Mon, 17 Oct 2022 08:46:59 +0000 (GMT) [thread overview] Message-ID: <20221017084659.A749B3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:0f4815502d8dac07579dc7a5a40c597a18291b4c commit r13-3325-g0f4815502d8dac07579dc7a5a40c597a18291b4c Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Oct 17 09:38:02 2022 +0100 libstdc++: Fix value of __cpp_lib_constexpr_charconv libstdc++-v3/ChangeLog: * include/std/charconv (__cpp_lib_constexpr_charconv): Define to correct value. * include/std/version (__cpp_lib_constexpr_charconv): Likewise. * testsuite/20_util/to_chars/constexpr.cc: Check correct value. * testsuite/20_util/to_chars/version.cc: Likewise. Diff: --- libstdc++-v3/include/std/charconv | 2 +- libstdc++-v3/include/std/version | 2 +- libstdc++-v3/testsuite/20_util/to_chars/constexpr.cc | 2 +- libstdc++-v3/testsuite/20_util/to_chars/version.cc | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/include/std/charconv b/libstdc++-v3/include/std/charconv index 4b6cc83a567..7aefdd3298c 100644 --- a/libstdc++-v3/include/std/charconv +++ b/libstdc++-v3/include/std/charconv @@ -51,7 +51,7 @@ #endif #if __cplusplus > 202002L -# define __cpp_lib_constexpr_charconv 202202L +# define __cpp_lib_constexpr_charconv 202207L #endif namespace std _GLIBCXX_VISIBILITY(default) diff --git a/libstdc++-v3/include/std/version b/libstdc++-v3/include/std/version index bec9e7aa792..3c7c440bd80 100644 --- a/libstdc++-v3/include/std/version +++ b/libstdc++-v3/include/std/version @@ -302,7 +302,7 @@ #if __cplusplus > 202002L // c++23 #define __cpp_lib_byteswap 202110L -#define __cpp_lib_constexpr_charconv 202202L +#define __cpp_lib_constexpr_charconv 202207L #define __cpp_lib_constexpr_typeinfo 202106L #if __cpp_concepts >= 202002L # define __cpp_lib_expected 202202L diff --git a/libstdc++-v3/testsuite/20_util/to_chars/constexpr.cc b/libstdc++-v3/testsuite/20_util/to_chars/constexpr.cc index 30c591659ee..10855b737c7 100644 --- a/libstdc++-v3/testsuite/20_util/to_chars/constexpr.cc +++ b/libstdc++-v3/testsuite/20_util/to_chars/constexpr.cc @@ -5,7 +5,7 @@ #ifndef __cpp_lib_constexpr_charconv # error "Feature-test macro for constexpr charconv missing in <charconv>" -#elif __cpp_lib_constexpr_charconv != 202202L +#elif __cpp_lib_constexpr_charconv != 202207L # error "Feature-test macro for constexpr charconv has wrong value in <charconv>" #endif diff --git a/libstdc++-v3/testsuite/20_util/to_chars/version.cc b/libstdc++-v3/testsuite/20_util/to_chars/version.cc index af06e1bf054..25b1e0036e8 100644 --- a/libstdc++-v3/testsuite/20_util/to_chars/version.cc +++ b/libstdc++-v3/testsuite/20_util/to_chars/version.cc @@ -11,6 +11,6 @@ #ifndef __cpp_lib_constexpr_charconv # error "Feature-test macro for constexpr charconv missing in <version>" -#elif __cpp_lib_constexpr_charconv != 202202L +#elif __cpp_lib_constexpr_charconv != 202207L # error "Feature-test macro for constexpr charconv has wrong value in <version>" #endif
reply other threads:[~2022-10-17 8:46 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=20221017084659.A749B3858D28@sourceware.org \ --to=redi@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).