public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104476] [11 Regression] using-decl shadowed by member function when in incomplete-class context Date: Tue, 12 Apr 2022 20:18:55 +0000 [thread overview] Message-ID: <bug-104476-4-qsU79dmkKL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104476 --- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> --- I'm not sure whether it makes more sense to revert the PR92918 patch on the 11 branch or leave it alone; the GCC 12 fix is too complex to backport. I guess I lean toward leaving it alone, since this hasn't gotten other reports.
next prev parent reply other threads:[~2022-04-12 20:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-09 19:40 [Bug c++/104476] New: " ppalka at gcc dot gnu.org 2022-02-09 20:12 ` [Bug c++/104476] [11/12 Regression] " pinskia at gcc dot gnu.org 2022-02-09 20:25 ` ppalka at gcc dot gnu.org 2022-02-09 20:36 ` [Bug c++/104476] [10/11/12 " ppalka at gcc dot gnu.org 2022-02-10 0:06 ` pinskia at gcc dot gnu.org 2022-02-10 7:09 ` rguenth at gcc dot gnu.org 2022-02-17 22:58 ` jason at gcc dot gnu.org 2022-02-17 23:13 ` cvs-commit at gcc dot gnu.org 2022-02-17 23:14 ` [Bug c++/104476] [11/12 " jason at gcc dot gnu.org 2022-03-18 18:08 ` cvs-commit at gcc dot gnu.org 2022-03-18 18:09 ` [Bug c++/104476] [11 " jason at gcc dot gnu.org 2022-04-07 8:38 ` rguenth at gcc dot gnu.org 2022-04-12 20:18 ` jason at gcc dot gnu.org [this message] 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2022-05-13 15:35 ` jason 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-104476-4-qsU79dmkKL@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).