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++/96749] [coroutines] unexpected 'warning: statement has no effect [-Wunused-value]' Date: Mon, 22 Mar 2021 22:04:18 +0000 [thread overview] Message-ID: <bug-96749-4-p2kIplL5ku@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96749-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96749 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:8fba8178ac49493ed7998fb9008810aac8138c19 commit r10-9515-g8fba8178ac49493ed7998fb9008810aac8138c19 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Tue Mar 2 10:12:58 2021 +0000 coroutines : Avoid generating empty statements [PR96749]. In the compiler-only idiom: " a = (target expr creats temp, op uses temp) " the target expression variable needs to be promoted to a frame one (if the expression has a suspend point). However, the only uses of the var are in the second part of the compound expression - and we were creating an empty statement corresponding to the (now unused) first arm. This then produces the spurious warnings noted. Fixed by avoiding generation of a separate variable nest for isolated target expressions (or similarly isolated co_awaits used in a function call). gcc/cp/ChangeLog: PR c++/96749 * coroutines.cc (flatten_await_stmt): Allow for the case where a target expression variable only has uses in the second part of a compound expression. (maybe_promote_temps): Avoid emiting empty statements. gcc/testsuite/ChangeLog: PR c++/96749 * g++.dg/coroutines/pr96749-1.C: New test. * g++.dg/coroutines/pr96749-2.C: New test. (cherry picked from commit ed8198461735f9b5b3c2cbe50f9913690ce4b4ca)
next prev parent reply other threads:[~2021-03-22 22:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-23 5:57 [Bug c++/96749] New: " bazhenov.dn at gmail dot com 2020-08-23 5:59 ` [Bug c++/96749] " bazhenov.dn at gmail dot com 2020-12-04 14:13 ` max at duempel dot org 2021-03-04 20:38 ` iains at gcc dot gnu.org 2021-03-12 15:36 ` iains at gcc dot gnu.org 2021-03-15 15:49 ` cvs-commit at gcc dot gnu.org 2021-03-22 22:04 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-24 12:38 ` iains 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-96749-4-p2kIplL5ku@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).