public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/41437] No access control for classes in template functions Date: Tue, 16 Jun 2020 13:02:05 +0000 [thread overview] Message-ID: <bug-41437-4-utSKXswho0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41437-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41437 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #13 from Patrick Palka <ppalka at gcc dot gnu.org> --- This should be fixed for GCC 11 now.
next prev parent reply other threads:[~2020-06-16 13:02 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41437-4@http.gcc.gnu.org/bugzilla/> 2010-09-24 10:05 ` [Bug 41437] (c++) " redi at gcc dot gnu.org 2012-02-24 16:52 ` [Bug c++/41437] " redi at gcc dot gnu.org 2013-06-21 18:17 ` w.shane.grant at gmail dot com 2014-12-08 10:28 ` redi at gcc dot gnu.org 2020-03-12 16:05 ` redi at gcc dot gnu.org 2020-05-19 13:20 ` ppalka at gcc dot gnu.org 2020-06-16 12:59 ` cvs-commit at gcc dot gnu.org 2020-06-16 12:59 ` cvs-commit at gcc dot gnu.org 2020-06-16 13:02 ` ppalka at gcc dot gnu.org [this message] 2020-06-16 13:03 ` ppalka at gcc dot gnu.org 2020-06-16 14:30 ` redi at gcc dot gnu.org 2021-01-19 21:20 ` cvs-commit at gcc dot gnu.org 2021-08-04 11:40 ` redi at gcc dot gnu.org 2021-08-27 18:15 ` pinskia at gcc dot gnu.org 2021-11-05 23:18 ` timturnerc at yahoo dot com 2009-09-22 20:10 [Bug c++/41437] New: " guillaume dot melquiond at inria dot fr 2009-09-25 4:44 ` [Bug c++/41437] " pinskia at gcc dot gnu dot org 2010-09-20 15:53 ` redi at gcc dot gnu dot org 2010-09-20 15:54 ` redi 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-41437-4-utSKXswho0@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).