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 c++/95822] [coroutines] compiler internal error with local object with noexcept false destructor Date: Thu, 25 Feb 2021 19:34:29 +0000 [thread overview] Message-ID: <bug-95822-4-3OPNGUfGxu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95822-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95822 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:7005a50d0121954031a223ea5a6c57aaa7e3efd3 commit r11-7402-g7005a50d0121954031a223ea5a6c57aaa7e3efd3 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Tue Feb 16 09:07:32 2021 +0000 coroutines : Remove throwing_cleanup marks from the ramp [PR95822]. The FE contains a mechanism for cleaning up return expressions if a function throws during the execution of cleanups prior to the return. If the original function has a return value with a non-trivial DTOR and the body contains a var with a DTOR that might throw, the function decl is marked "throwing_cleanup". However, we do not [in the coroutine ramp function, which is synthesised], use any body var types with DTORs that might throw. The original body [which will then contain the type with the throwing DTOR] is transformed into the actor function which only contains void returns, and is also wrapped in a try-catch block. So (a) the 'throwing_cleanup' is no longer correct for the ramp and (b) we do not need to transfer it to the actor which only contains void returns. gcc/cp/ChangeLog: PR c++/95822 * coroutines.cc (morph_fn_to_coro): Unconditionally remove any set throwing_cleanup marker. gcc/testsuite/ChangeLog: PR c++/95822 * g++.dg/coroutines/pr95822.C: New test.
next prev parent reply other threads:[~2021-02-25 19:34 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-22 18:51 [Bug c++/95822] New: " victor.burckel at gmail dot com 2020-06-23 9:06 ` [Bug c++/95822] " iains at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2021-02-16 9:12 ` iains at gcc dot gnu.org 2021-02-25 19:34 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-22 22:03 ` cvs-commit at gcc dot gnu.org 2021-03-24 12:42 ` iains at gcc dot gnu.org 2021-07-18 23:48 ` pinskia 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-95822-4-3OPNGUfGxu@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).