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++/111826] __cpp_lib_format should be 202110, not 202106 Date: Sat, 09 Dec 2023 22:04:56 +0000 [thread overview] Message-ID: <bug-111826-4-2UmNbSsmPt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111826-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111826 --- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: 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)
next prev parent reply other threads:[~2023-12-09 22:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-15 21:39 [Bug libstdc++/111826] New: " bbi5291 at gmail dot com 2023-10-16 8:45 ` [Bug libstdc++/111826] " redi at gcc dot gnu.org 2023-12-08 14:44 ` redi at gcc dot gnu.org 2023-12-09 14:07 ` cvs-commit at gcc dot gnu.org 2023-12-09 22:04 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-09 22:05 ` 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-111826-4-2UmNbSsmPt@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).