From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: __vic <victor.dyachenko@protonmail.com>, victor@westerhu.is
Subject: Re: [committed] libstdc++: Fix noexcept on dtors in <experimental/scope> [PR114152]
Date: Wed, 28 Feb 2024 14:54:08 +0000 [thread overview]
Message-ID: <CACb0b4=_U5ydQEwL3Gf8gbLSCocueXU2XVMv5dijvMwEHFS4Pg@mail.gmail.com> (raw)
In-Reply-To: <20240228145234.214146-1-jwakely@redhat.com>
Oops, sorry, I CC'd the wrong Victor on this patch (you've both
reported libstdc++ bugs today and I grabbed the email address from the
wrong browser tab).
On Wed, 28 Feb 2024 at 14:53, Jonathan Wakely wrote:
>
> Tested x86_64-linux, pushed to trunk. Backport to gcc-13 to follow.
>
> -- >8 --
>
> 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.
> ---
> libstdc++-v3/include/experimental/scope | 6 ++---
> .../experimental/scopeguard/114152.cc | 24 +++++++++++++++++++
> 2 files changed, 27 insertions(+), 3 deletions(-)
> create mode 100644 libstdc++-v3/testsuite/experimental/scopeguard/114152.cc
>
> diff --git a/libstdc++-v3/include/experimental/scope b/libstdc++-v3/include/experimental/scope
> index 5dbeac14795..ea273e8c095 100644
> --- a/libstdc++-v3/include/experimental/scope
> +++ b/libstdc++-v3/include/experimental/scope
> @@ -97,7 +97,7 @@ namespace experimental::inline fundamentals_v3
> scope_exit& operator=(const scope_exit&) = delete;
> scope_exit& operator=(scope_exit&&) = delete;
>
> - ~scope_exit() noexcept(noexcept(this->_M_exit_function))
> + ~scope_exit() noexcept
> {
> if (_M_execute_on_destruction)
> _M_exit_function();
> @@ -157,7 +157,7 @@ namespace experimental::inline fundamentals_v3
> scope_fail& operator=(const scope_fail&) = delete;
> scope_fail& operator=(scope_fail&&) = delete;
>
> - ~scope_fail() noexcept(noexcept(this->_M_exit_function))
> + ~scope_fail() noexcept
> {
> if (std::uncaught_exceptions() > _M_uncaught_init)
> _M_exit_function();
> @@ -211,7 +211,7 @@ namespace experimental::inline fundamentals_v3
> scope_success& operator=(const scope_success&) = delete;
> scope_success& operator=(scope_success&&) = delete;
>
> - ~scope_success() noexcept(noexcept(this->_M_exit_function))
> + ~scope_success() noexcept(noexcept(this->_M_exit_function()))
> {
> if (std::uncaught_exceptions() <= _M_uncaught_init)
> _M_exit_function();
> diff --git a/libstdc++-v3/testsuite/experimental/scopeguard/114152.cc b/libstdc++-v3/testsuite/experimental/scopeguard/114152.cc
> new file mode 100644
> index 00000000000..63c1f710e9f
> --- /dev/null
> +++ b/libstdc++-v3/testsuite/experimental/scopeguard/114152.cc
> @@ -0,0 +1,24 @@
> +// { dg-do compile { target c++20 } }
> +
> +// PR libstdc++/114152
> +// Wrong exception specifiers for LFTSv3 scope guard destructors
> +
> +#include <experimental/scope>
> +
> +using namespace std::experimental;
> +
> +struct F {
> + void operator()() noexcept(false);
> +};
> +
> +static_assert( noexcept(std::declval<scope_exit<F>&>().~scope_exit()) );
> +static_assert( noexcept(std::declval<scope_fail<F>&>().~scope_fail()) );
> +static_assert( ! noexcept(std::declval<scope_success<F>&>().~scope_success()) );
> +
> +struct G {
> + void operator()() noexcept(true);
> +};
> +
> +static_assert( noexcept(std::declval<scope_exit<G>&>().~scope_exit()) );
> +static_assert( noexcept(std::declval<scope_fail<G>&>().~scope_fail()) );
> +static_assert( noexcept(std::declval<scope_success<G>&>().~scope_success()) );
> --
> 2.43.0
>
prev parent reply other threads:[~2024-02-28 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:51 Jonathan Wakely
2024-02-28 14:54 ` Jonathan Wakely [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='CACb0b4=_U5ydQEwL3Gf8gbLSCocueXU2XVMv5dijvMwEHFS4Pg@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=victor.dyachenko@protonmail.com \
--cc=victor@westerhu.is \
/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).