public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108797] [10/11 Regression] libstdc++: Inconsistent noexcept-specifier for valarray begin/end
Date: Wed, 15 Feb 2023 07:51:40 +0000 [thread overview]
Message-ID: <bug-108797-4-giwqKsRGJs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108797-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108797
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Known to work| |10.3.0, 11.3.0, 12.1.0,
| |9.4.0
Summary|libstdc++: Inconsistent |[10/11 Regression]
|noexcept-specifier for |libstdc++: Inconsistent
|valarray begin/end |noexcept-specifier for
| |valarray begin/end
Status|UNCONFIRMED |RESOLVED
Target Milestone|--- |10.5
Known to fail| |10.4.0, 9.5.0
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The last GCC 9.x was GCC 9.5 released 2022-05-27.
The ship has sailed to apply patches to the GCC 9 branch now too.
Just for reference GCC 10 branch was applied r10-10910-g32bbf76e4345a7
GCC 11: r11-9264-g423cd47cfc9640 .
next prev parent reply other threads:[~2023-02-15 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 7:39 [Bug libstdc++/108797] New: libstdc++: Inconsistent noexcept-specific " holger.k at elberer dot de
2023-02-15 7:51 ` pinskia at gcc dot gnu.org [this message]
2023-02-15 7:56 ` [Bug libstdc++/108797] [10/11 Regression] libstdc++: Inconsistent noexcept-specifier " holger.k at elberer dot de
2023-02-15 8:22 ` pinskia at gcc dot gnu.org
2023-02-15 8:28 ` holger.k at elberer dot 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-108797-4-giwqKsRGJs@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).