From: Jonathan Wakely <jwakely@redhat.com>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Fix iterator caching inside range adaptors [PR100479]
Date: Mon, 17 May 2021 17:51:47 +0100 [thread overview]
Message-ID: <YKKfI4l4Ac5ahVd4@redhat.com> (raw)
In-Reply-To: <20210517154302.840608-1-ppalka@redhat.com>
On 17/05/21 11:43 -0400, Patrick Palka via Libstdc++ wrote:
>This fixes two issues with our iterator caching as described in detail
>in the PR. Since r12-336 added the __non_propagating_cache class
>template as part of P2328, this patch just rewrites the _CachedPosition
>partial specialization in terms of this class template.
>
>Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
OK, thanks.
>Shall we
>also backport this?
I think so, but give it a couple of weeks (or more) on trunk first.
next prev parent reply other threads:[~2021-05-17 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:43 Patrick Palka
2021-05-17 16:51 ` Jonathan Wakely [this message]
2021-05-17 18:39 ` Tim Song
2021-05-17 19:59 ` Patrick Palka
2021-05-17 22:28 ` Tim Song
2021-05-18 4:53 ` Patrick Palka
2021-05-24 18:59 ` 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=YKKfI4l4Ac5ahVd4@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=ppalka@redhat.com \
/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).