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++/96029] [8/9 Regression] Inconsistencies with associative/unordered containers
Date: Thu, 08 Apr 2021 17:43:13 +0000	[thread overview]
Message-ID: <bug-96029-4-KGP5JZp63k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96029-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[8/9/10 Regression]         |[8/9 Regression]
                   |Inconsistencies with        |Inconsistencies with
                   |associative/unordered       |associative/unordered
                   |containers                  |containers

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 10.4 too.

  parent reply	other threads:[~2021-04-08 17:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 11:38 [Bug libstdc++/96029] New: " nknikita at niisi dot ras.ru
2020-07-02 12:44 ` [Bug libstdc++/96029] [8/9/10/11 Regression] " redi at gcc dot gnu.org
2020-07-02 13:24 ` rguenth at gcc dot gnu.org
2020-10-12 12:50 ` rguenth at gcc dot gnu.org
2021-04-08 14:35 ` [Bug libstdc++/96029] [8/9/10 " redi at gcc dot gnu.org
2021-04-08 17:00 ` cvs-commit at gcc dot gnu.org
2021-04-08 17:00 ` cvs-commit at gcc dot gnu.org
2021-04-08 17:43 ` redi at gcc dot gnu.org [this message]
2021-04-08 23:37 ` [Bug libstdc++/96029] [8/9 " cvs-commit at gcc dot gnu.org
2021-04-08 23:37 ` cvs-commit at gcc dot gnu.org
2021-04-08 23:38 ` [Bug libstdc++/96029] [8 " redi at gcc dot gnu.org
2021-04-09 14:04 ` vvinayag at arm dot com
2021-04-09 14:22 ` redi at gcc dot gnu.org
2021-05-14 13:58 ` jakub 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-96029-4-KGP5JZp63k@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).