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++/95711] namespace alias fails inside coroutine Date: Tue, 30 Jun 2020 12:46:33 +0000 [thread overview] Message-ID: <bug-95711-4-4o0sRkUYpC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95711-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95711 --- Comment #4 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:65025a6dae4b2c62ca79d2d0687229dafa93af7f commit r10-8395-g65025a6dae4b2c62ca79d2d0687229dafa93af7f Author: Iain Sandoe <iain@sandoe.co.uk> Date: Tue Jun 30 08:29:11 2020 +0100 coroutines: Handle namespaces while scanning local vars [PR95711]. We need to skip past namespace decls when scanning the bind expression var lists checking for local vars. gcc/cp/ChangeLog: PR c++/95711 * coroutines.cc (register_local_var_uses): Skip past namespace decls. gcc/testsuite/ChangeLog: PR c++/95711 * g++.dg/coroutines/pr95711.C: New test. (cherry picked from commit 06ed4aae1c2fa84b7050a286d866db4a6def3c36)
next prev parent reply other threads:[~2020-06-30 12:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-16 19:01 [Bug c++/95711] New: " alejandromagic at hotmail dot com 2020-06-16 21:28 ` [Bug c++/95711] " alejandromagic at hotmail dot com 2020-06-21 12:59 ` iains at gcc dot gnu.org 2020-06-28 12:52 ` cvs-commit at gcc dot gnu.org 2020-06-30 12:46 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-30 12:50 ` 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-95711-4-4o0sRkUYpC@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).