public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114152] Wrong exception specifiers for LFTSv3 scope guard destructors Date: Fri, 01 Mar 2024 10:52:48 +0000 [thread overview] Message-ID: <bug-114152-4-mIAMPR1WCF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114152-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114152 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:89e7b77df1aefb01aadfacae83170b24a4c4d274 commit r13-8371-g89e7b77df1aefb01aadfacae83170b24a4c4d274 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Feb 28 14:45:18 2024 +0000 libstdc++: Fix noexcept on dtors in <experimental/scope> [PR114152] The PR points out that the destructors all have incorrect noexcept-specifiers. libstdc++-v3/ChangeLog: PR libstdc++/114152 * include/experimental/scope (scope_exit scope_fail): Make destructor unconditionally noexcept. (scope_sucess): Fix noexcept-specifier. * testsuite/experimental/scopeguard/114152.cc: New test. (cherry picked from commit 80c386cb20d38ebc55f30a79418fabfbed904b87)
next prev parent reply other threads:[~2024-03-01 10:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 14:17 [Bug libstdc++/114152] New: " victor at westerhu dot is 2024-02-28 14:40 ` [Bug libstdc++/114152] " redi at gcc dot gnu.org 2024-02-28 14:42 ` victor at westerhu dot is 2024-02-28 14:47 ` redi at gcc dot gnu.org 2024-02-28 14:50 ` redi at gcc dot gnu.org 2024-02-28 14:51 ` cvs-commit at gcc dot gnu.org 2024-03-01 10:52 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-01 10:53 ` redi 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-114152-4-mIAMPR1WCF@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: linkBe 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).