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++/100631] ranges::elements_view:: _Sentinel is missing __distance_from() that can access _M_current of _Iterator
Date: Thu, 10 Jun 2021 18:54:33 +0000	[thread overview]
Message-ID: <bug-100631-4-isdiENez45@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100631-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100631

--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:3b93d61be5a5a93e95783b80c58b297e215badf1

commit r11-8542-g3b93d61be5a5a93e95783b80c58b297e215badf1
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue May 18 10:21:27 2021 -0400

    libstdc++: Fix access issue in elements_view::_Sentinel [PR100631]

    In the earlier commit r12-854 I forgot to also rewrite the other operator-
    overload in terms of the split-out member function _M_distance_from.

    libstdc++-v3/ChangeLog:

            PR libstdc++/100631
            * include/std/ranges (elements_view::_Sentinel::operator-): Use
            _M_distance_from in the other operator- overload too.
            * testsuite/std/ranges/adaptors/elements.cc (test06): Augment test.

    (cherry picked from commit 38751c4d5e15bd1c682ac4c868a2c4ce48ca5503)

  parent reply	other threads:[~2021-06-10 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  3:22 [Bug libstdc++/100631] New: " hewillk at gmail dot com
2021-05-17  3:45 ` [Bug libstdc++/100631] " hewillk at gmail dot com
2021-05-17  4:50 ` hewillk at gmail dot com
2021-05-17 10:29 ` ppalka at gcc dot gnu.org
2021-05-17 12:32 ` rs2740 at gmail dot com
2021-05-17 13:34 ` hewillk at gmail dot com
2021-05-18  4:35 ` cvs-commit at gcc dot gnu.org
2021-05-18  5:32 ` hewillk at gmail dot com
2021-05-18 13:50 ` ppalka at gcc dot gnu.org
2021-05-18 14:22 ` cvs-commit at gcc dot gnu.org
2021-06-10 18:54 ` cvs-commit at gcc dot gnu.org
2021-06-10 18:54 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-10 18:57 ` cvs-commit at gcc dot gnu.org
2021-06-10 18:58 ` cvs-commit at gcc dot gnu.org
2021-06-10 18:58 ` ppalka 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-100631-4-isdiENez45@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: 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).