public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/102358] niter_base and miter_base overloaded for move_iterator missing constexpr
Date: Sat, 25 Sep 2021 20:06:39 +0000	[thread overview]
Message-ID: <bug-102358-4-flKnHR2dJQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102358-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-09-25
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

  reply	other threads:[~2021-09-25 20:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16  7:38 [Bug libstdc++/102358] New: " hewillk at gmail dot com
2021-09-25 20:06 ` redi at gcc dot gnu.org [this message]
2021-10-21 12:31 ` [Bug libstdc++/102358] " ppalka at gcc dot gnu.org
2021-10-21 16:13 ` cvs-commit at gcc dot gnu.org
2022-02-16 21:43 ` gcc at ebasoft dot com.pl
2022-02-17 10:29 ` redi at gcc dot gnu.org
2022-02-17 10:53 ` gcc at ebasoft dot com.pl
2022-02-17 11:40 ` redi at gcc dot gnu.org
2022-02-17 11:50 ` gcc at ebasoft dot com.pl
2022-02-17 12:37 ` redi at gcc dot gnu.org
2022-02-17 13:03 ` cvs-commit at gcc dot gnu.org
2022-02-17 13:04 ` cvs-commit at gcc dot gnu.org
2022-02-17 13:06 ` 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-102358-4-flKnHR2dJQ@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).