public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95983] `std::counted_iterator<std::iterator_t<std::ranges::basic_istream_view<...>>>` fails to satisfy `std::input_or_output_iterator`
Date: Tue, 20 Apr 2021 15:59:50 +0000	[thread overview]
Message-ID: <bug-95983-4-Ig9IaC5vAl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95983-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to gcc-bugs from comment #4)
> Hi Patrick,
> 
> thank you for that patch. I guess that it also fixes
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96070.

Ah indeed, thanks.  The testcase there seems similar enough to mark the PR as a
dup of this one.

> 
> Will this patch be backported to gcc-10?

I believe so; fortunately, the patch applies pretty cleanly to the 10 branch,
so I don't expect many changes will be needed in order to backport.

  parent reply	other threads:[~2021-04-20 15:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 18:19 [Bug libstdc++/95983] New: " ensadc at mailnesia dot com
2020-07-08 14:56 ` [Bug libstdc++/95983] " redi at gcc dot gnu.org
2020-07-27  5:07 ` ensadc at mailnesia dot com
2021-04-19 10:40 ` redi at gcc dot gnu.org
2021-04-20  3:52 ` ppalka at gcc dot gnu.org
2021-04-20  7:45 ` gcc-bugs at marehr dot dialup.fu-berlin.de
2021-04-20 13:19 ` cvs-commit at gcc dot gnu.org
2021-04-20 13:20 ` cvs-commit at gcc dot gnu.org
2021-04-20 15:39 ` ppalka at gcc dot gnu.org
2021-04-20 15:59 ` ppalka at gcc dot gnu.org [this message]
2021-05-04 13:51 ` cvs-commit at gcc dot gnu.org
2021-05-04 13:52 ` ppalka at gcc dot gnu.org
2021-05-04 20:21 ` gcc-bugs at marehr dot dialup.fu-berlin.de

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-95983-4-Ig9IaC5vAl@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).