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-8140] libstdc++: Fix value of __cpp_lib_format macro [PR111826] Date: Sat, 9 Dec 2023 22:04:55 +0000 (GMT) [thread overview] Message-ID: <20231209220455.69EA1385842B@sourceware.org> (raw) https://gcc.gnu.org/g:9f5011f9e6e347e0b91f47a118a0ce58a2c2d99a commit r13-8140-g9f5011f9e6e347e0b91f47a118a0ce58a2c2d99a Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Dec 8 14:40:26 2023 +0000 libstdc++: Fix value of __cpp_lib_format macro [PR111826] As noted in the PR, we support both features required for the 202110L value, so we should define it with that value. libstdc++-v3/ChangeLog: PR libstdc++/111826 * include/std/format (__cpp_lib_format): Update value. * include/std/version (__cpp_lib_format): Likewise. * testsuite/std/format/functions/format.cc: Update expected value. (cherry picked from commit cdf45e00a936a76a785c592c9730f24ef1ac25cd) Diff: --- libstdc++-v3/include/std/format | 2 +- libstdc++-v3/include/std/version | 2 +- libstdc++-v3/testsuite/std/format/functions/format.cc | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/include/std/format b/libstdc++-v3/include/std/format index 88510ccf60e..f454c49e12d 100644 --- a/libstdc++-v3/include/std/format +++ b/libstdc++-v3/include/std/format @@ -64,7 +64,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION // 202106 std::format improvements. // 202110 Fixing locale handling in chrono formatters, generator-like types. // 202207 Encodings in localized formatting of chrono, basic-format-string. -#define __cpp_lib_format 202106L +#define __cpp_lib_format 202110L #if __cplusplus > 202002L // 202207 P2286R8 Formatting Ranges diff --git a/libstdc++-v3/include/std/version b/libstdc++-v3/include/std/version index 02ead8f1443..31e79bc6f40 100644 --- a/libstdc++-v3/include/std/version +++ b/libstdc++-v3/include/std/version @@ -294,7 +294,7 @@ #endif #define __cpp_lib_constexpr_vector 201907L #define __cpp_lib_erase_if 202002L -#define __cpp_lib_format 202106L +#define __cpp_lib_format 202110L #define __cpp_lib_generic_unordered_lookup 201811L #ifdef _GLIBCXX_HAS_GTHREADS # define __cpp_lib_jthread 201911L diff --git a/libstdc++-v3/testsuite/std/format/functions/format.cc b/libstdc++-v3/testsuite/std/format/functions/format.cc index 59ed3be8baa..b8ad4f1ed29 100644 --- a/libstdc++-v3/testsuite/std/format/functions/format.cc +++ b/libstdc++-v3/testsuite/std/format/functions/format.cc @@ -6,7 +6,7 @@ #ifndef __cpp_lib_format # error "Feature test macro for std::format is missing in <format>" -#elif __cpp_lib_format < 202106L +#elif __cpp_lib_format < 202110L # error "Feature test macro for std::format has wrong value in <format>" #endif @@ -14,7 +14,7 @@ #include <version> #ifndef __cpp_lib_format # error "Feature test macro for std::format is missing in <version>" -#elif __cpp_lib_format < 202106L +#elif __cpp_lib_format < 202110L # error "Feature test macro for std::format has wrong value in <version>" #endif
reply other threads:[~2023-12-09 22:04 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=20231209220455.69EA1385842B@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).