public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100409] C++ FE elides pure throwing call Date: Thu, 08 Jul 2021 07:25:24 +0000 [thread overview] Message-ID: <bug-100409-4-O36UMR5eKW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100409 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- So I'm looking again at this. For the simple cases I have at hand we can fix the C++ FE issue with diff --git a/gcc/cp/cvt.c b/gcc/cp/cvt.c index d035e611be4..81097942449 100644 --- a/gcc/cp/cvt.c +++ b/gcc/cp/cvt.c @@ -1645,7 +1645,12 @@ convert_to_void (tree expr, impl_conv_void implicit, tsub st_flags_t complain) } expr = build1 (CONVERT_EXPR, void_type_node, expr); } - if (! TREE_SIDE_EFFECTS (expr)) + if (! TREE_SIDE_EFFECTS (expr) + && ! (CONVERT_EXPR_P (expr) + && TREE_CODE (TREE_OPERAND (expr, 0)) == CALL_EXPR + && ! TREE_NOTHROW (TREE_OPERAND (expr, 0))) + && ! (TREE_CODE (expr) == CALL_EXPR + && ! TREE_NOTHROW (expr))) expr = void_node; return expr; } of course that relies on seeing f() or (void)f(), it already fails with (void)(1 + f()). We also diagnose such stmts as having no effect: t.ii: In function 'int bar(int*, int)': t.ii:13:10: warning: statement has no effect [-Wunused-value] 13 | 1 + foo (n); | ~~^~~~~~~~~ there's expr_noexcept_p that seems to work here even for 1 + foo () but I'm not sure it's the correct tool. But it would simplify a fix to diff --git a/gcc/cp/cvt.c b/gcc/cp/cvt.c index d035e611be4..4885a7c6584 100644 --- a/gcc/cp/cvt.c +++ b/gcc/cp/cvt.c @@ -1645,7 +1645,7 @@ convert_to_void (tree expr, impl_conv_void implicit, tsubst_flags_t complain) } expr = build1 (CONVERT_EXPR, void_type_node, expr); } - if (! TREE_SIDE_EFFECTS (expr)) + if (! TREE_SIDE_EFFECTS (expr) && expr_noexcept_p (expr, 0)) expr = void_node; return expr; } I'm giving that full testing.
next prev parent reply other threads:[~2021-07-08 7:25 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 6:45 [Bug c++/100409] New: " rguenth at gcc dot gnu.org 2021-05-04 6:46 ` [Bug c++/100409] " rguenth at gcc dot gnu.org 2021-05-05 8:02 ` rguenth at gcc dot gnu.org 2021-07-08 7:25 ` rguenth at gcc dot gnu.org [this message] 2021-07-08 8:19 ` harald at gigawatt dot nl 2021-07-08 8:38 ` rguenth at gcc dot gnu.org 2021-07-08 8:38 ` rguenth at gcc dot gnu.org 2021-07-08 8:39 ` rguenth at gcc dot gnu.org 2021-07-08 8:44 ` rguenth at gcc dot gnu.org 2021-07-08 9:17 ` harald at gigawatt dot nl 2021-07-08 9:20 ` rguenth at gcc dot gnu.org 2021-07-08 9:41 ` rguenth at gcc dot gnu.org 2021-07-08 13:15 ` mpolacek at gcc dot gnu.org 2021-07-08 13:53 ` jason at gcc dot gnu.org 2021-07-08 14:09 ` rguenth at gcc dot gnu.org 2021-07-08 15:13 ` jason at gcc dot gnu.org 2021-07-08 22:06 ` mpolacek at gcc dot gnu.org 2022-01-05 14:41 ` rguenth 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-100409-4-O36UMR5eKW@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).