public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anthonysharp15 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19377] Using declaration in "private" part causes "protected" diagnostic
Date: Wed, 28 Apr 2021 18:48:02 +0000 [thread overview]
Message-ID: <bug-19377-4-xwcoeGlg7p@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-19377-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19377
--- Comment #15 from Anthony Sharp <anthonysharp15 at gmail dot com> ---
This should now be fixed as part of my patch:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=be246ac2d26e1cb072f205bf97d5eac150220f3f
next prev parent reply other threads:[~2021-04-28 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19377-4@http.gcc.gnu.org/bugzilla/>
2010-11-12 15:08 ` fabien at gcc dot gnu.org
2011-11-27 21:44 ` fabien at gcc dot gnu.org
2012-04-15 17:11 ` manu at gcc dot gnu.org
2012-04-15 17:18 ` pinskia at gcc dot gnu.org
2012-04-15 17:42 ` manu at gcc dot gnu.org
2012-04-15 18:24 ` fabien at gcc dot gnu.org
2014-02-06 14:22 ` abel at gcc dot gnu.org
2014-02-06 16:20 ` fabien at gcc dot gnu.org
2014-02-07 5:12 ` abel at gcc dot gnu.org
2014-02-08 8:44 ` harald at gigawatt dot nl
2014-02-08 15:57 ` redi at gcc dot gnu.org
2021-01-29 12:22 ` anthonysharp15 at gmail dot com
2021-04-28 18:48 ` anthonysharp15 at gmail dot com [this message]
2005-01-11 16:25 [Bug c++/19377] New: " redi at gcc dot gnu dot org
2005-01-11 17:08 ` [Bug c++/19377] " pinskia at gcc dot gnu dot org
2005-01-12 10:46 ` lerdsuwa at gcc dot gnu dot org
2005-05-01 3:34 ` pinskia at gcc dot gnu dot 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-19377-4-xwcoeGlg7p@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: link
Be 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).