From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 1C603385800C for ; Fri, 11 Feb 2022 13:36:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1C603385800C Received: from mail-yb1-f200.google.com (mail-yb1-f200.google.com [209.85.219.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-417-BUbUNf6oMyyND4eH2IVpkA-1; Fri, 11 Feb 2022 08:36:07 -0500 X-MC-Unique: BUbUNf6oMyyND4eH2IVpkA-1 Received: by mail-yb1-f200.google.com with SMTP id j17-20020a25ec11000000b0061dabf74012so18771454ybh.15 for ; Fri, 11 Feb 2022 05:36:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=n2a4WYDmWHF4zKwbvrOxaOYrkRvq7MOE5aqfhD+pfrE=; b=LPfTx9AdfsYp+jYgxSjm3lJaJhMv7HC6p7swbJ5TeXs/GJOYz1xowrKXCUgiryb+zF m/bfsXBMLItOFIVQp+Mw5td6v+annn3+W/thAuCuo2WYIcEdCNOMugS/IPMXAhAaXszl vInoa9Wftq3tRd4fZpbNPdPKenMiIuga9fbqZJCCfQ2OQZx7/7nIBDGCxixJRD1oP6ok RYJuYD1mKPYHrqffW6KQ56M8SfHNTOM/98LehPdCxhA0zCSnAHyQcsVSTXe9YnHAYC+x MrfFblLqIAY3hFZTjRON9cLPqrAxbmjPct9c1KS0A1YBi+27uVByazS3E9TQQSN+pLfE uLug== X-Gm-Message-State: AOAM533l4CbLqbMxLodZYUq6A48D4M1A6vPDCqcBB9GvRLUUf6ruxGpZ D2qGMXk97+h9bbQS30HkhJ1p/KEoiPxawl59vOSv4zhijRZ4Dn59Xj+APiI0FNZsFNAFLS07a0a zrC3Azf6GhGRY3i780GkLSuvkoEsaet4= X-Received: by 2002:a81:c644:: with SMTP id q4mr1660985ywj.206.1644586567164; Fri, 11 Feb 2022 05:36:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJwadMfkvnSi1kcKvC0wKr6W7x2+M7NFyNrQtLfMhh1GI8Bv6WVr8uxpM/+jnAm6mSx6i0T7GNiuP1p/lxCyMZE= X-Received: by 2002:a81:c644:: with SMTP id q4mr1660970ywj.206.1644586566963; Fri, 11 Feb 2022 05:36:06 -0800 (PST) MIME-Version: 1.0 References: <20220210165624.2953676-1-ppalka@redhat.com> <20220210165624.2953676-2-ppalka@redhat.com> In-Reply-To: <20220210165624.2953676-2-ppalka@redhat.com> From: Jonathan Wakely Date: Fri, 11 Feb 2022 13:35:56 +0000 Message-ID: Subject: Re: [PATCH 2/3, 11 backport] libstdc++: Sync __cpp_lib_ranges macro defined in ranges_cmp.h To: Patrick Palka Cc: gcc Patches , "libstdc++" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-12.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2022 13:36:10 -0000 On Thu, 10 Feb 2022 at 17:01, Patrick Palka via Libstdc++ wrote: > > r12-1606 bumped the value of __cpp_lib_ranges defined in , > but this macro is also defined in , 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) OK, thanks. > --- > 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 >