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++/100690] ranges::iota_view::_Sentinel cannot access _M_current of _Iterator
Date: Thu, 10 Jun 2021 19:22:05 +0000 [thread overview]
Message-ID: <bug-100690-4-Vuuh6382WZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100690-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100690
--- Comment #2 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:c6ccaf17ddbe8adb76475826be02580790ab28ca
commit r11-8545-gc6ccaf17ddbe8adb76475826be02580790ab28ca
Author: Patrick Palka <ppalka@redhat.com>
Date: Thu May 20 23:39:05 2021 -0400
libstdc++: Fix access issue in iota_view::_Sentinel [PR100690]
libstdc++-v3/ChangeLog:
PR libstdc++/100690
* include/std/ranges (iota_view::_Sentinel::_M_distance_from):
Split out this member function from ...
(iota_view::_Sentinel::operator-): ... here, for sake of access
control.
* testsuite/std/ranges/iota/iota_view.cc (test05): New test.
(cherry picked from commit 317a38cd468d565dc8ce45c6da0dbccf38808f70)
next prev parent reply other threads:[~2021-06-10 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 3:45 [Bug libstdc++/100690] New: " hewillk at gmail dot com
2021-05-20 14:31 ` [Bug libstdc++/100690] " ppalka at gcc dot gnu.org
2021-05-21 3:39 ` cvs-commit at gcc dot gnu.org
2021-06-10 19:22 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-10 19:25 ` cvs-commit at gcc dot gnu.org
2021-06-10 19:26 ` 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-100690-4-Vuuh6382WZ@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).