public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/97930] pair is not a structural type
Date: Mon, 29 May 2023 10:03:28 +0000 [thread overview]
Message-ID: <bug-97930-4-41ES479LnM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97930-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97930
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|11.4 |11.5
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 11.4 is being released, retargeting bugs to GCC 11.5.
prev parent reply other threads:[~2023-05-29 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 18:03 [Bug libstdc++/97930] New: " stinkingmadgod at gmail dot com
2020-11-20 20:06 ` [Bug libstdc++/97930] " redi at gcc dot gnu.org
2020-11-20 20:07 ` redi at gcc dot gnu.org
2021-04-07 10:29 ` redi at gcc dot gnu.org
2021-04-28 17:17 ` cvs-commit at gcc dot gnu.org
2021-04-28 17:20 ` redi at gcc dot gnu.org
2021-07-28 7:04 ` rguenth at gcc dot gnu.org
2022-09-29 18:06 ` redi at gcc dot gnu.org
2023-05-29 10:03 ` jakub at gcc dot gnu.org [this message]
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-97930-4-41ES479LnM@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).