From: Patrick Palka <ppalka@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, Patrick Palka <ppalka@redhat.com>
Subject: [PATCH 2/3, 11 backport] libstdc++: Sync __cpp_lib_ranges macro defined in ranges_cmp.h
Date: Thu, 10 Feb 2022 11:56:23 -0500 [thread overview]
Message-ID: <20220210165624.2953676-2-ppalka@redhat.com> (raw)
In-Reply-To: <20220210165624.2953676-1-ppalka@redhat.com>
r12-1606 bumped the value of __cpp_lib_ranges defined in <version>,
but this macro is also defined in <bits/range_cmp.h>, so it needs to
be updated there as well.
PR libstdc++/103904
libstdc++-v3/ChangeLog:
* include/bits/ranges_cmp.h (__cpp_lib_ranges): Adjust value.
(cherry picked from commit 12bdd39755a25d237b7776153cbe03e171396fc5)
---
libstdc++-v3/include/bits/ranges_cmp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/include/bits/ranges_cmp.h b/libstdc++-v3/include/bits/ranges_cmp.h
index f859a33b2c1..1d7da30dddf 100644
--- a/libstdc++-v3/include/bits/ranges_cmp.h
+++ b/libstdc++-v3/include/bits/ranges_cmp.h
@@ -57,7 +57,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
#ifdef __cpp_lib_concepts
// Define this here, included by all the headers that need to define it.
-#define __cpp_lib_ranges 201911L
+#define __cpp_lib_ranges 202106L
namespace ranges
{
--
2.35.1.102.g2b9c120970
next prev parent reply other threads:[~2022-02-10 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 16:56 [PATCH 1/3, 11 backport] libstdc++: Implement P2325 changes to default-constructibility of views Patrick Palka
2022-02-10 16:56 ` Patrick Palka [this message]
2022-02-11 13:35 ` [PATCH 2/3, 11 backport] libstdc++: Sync __cpp_lib_ranges macro defined in ranges_cmp.h Jonathan Wakely
2022-02-10 16:56 ` [PATCH 3/3, 11 backport] libstdc++: invalid default init in _CachedPosition [PR101231] Patrick Palka
2022-02-11 13:36 ` Jonathan Wakely
2022-02-10 16:58 ` [PATCH 1/3, 11 backport] libstdc++: Implement P2325 changes to default-constructibility of views Patrick Palka
2022-02-10 17:27 ` Patrick Palka
2022-02-11 13:35 ` Jonathan Wakely
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=20220210165624.2953676-2-ppalka@redhat.com \
--to=ppalka@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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: link
Be 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).