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++/105752] Template function can access private member
Date: Thu, 02 Jun 2022 13:29:43 +0000 [thread overview]
Message-ID: <bug-105752-4-68Xt1CkdGx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105752-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105752
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
CC| |ppalka at gcc dot gnu.org
--- Comment #6 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Csaba Ráduly from comment #5)
> The fact that GCC 11 shows an error for the code in comment #4 suggests that
> this was a bug which was fixed. Does it ring a bell to anyone? This bug
> should probably marked as a duplicate, but of which other bug?
Looks like we started to correctly reject the comment #4 testcase after
r11-6800-g29853c653245c3. Since the testcase is pretty similar to the one from
PR58993, I guess we can mark this a dup of that PR.
*** This bug has been marked as a duplicate of bug 58993 ***
prev parent reply other threads:[~2022-06-02 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 16:36 [Bug c++/105752] New: " csaba_22 at yahoo dot co.uk
2022-05-27 16:40 ` [Bug c++/105752] " pinskia at gcc dot gnu.org
2022-05-27 17:12 ` redi at gcc dot gnu.org
2022-05-27 17:13 ` redi at gcc dot gnu.org
2022-05-30 17:49 ` csaba_22 at yahoo dot co.uk
2022-06-02 9:10 ` csaba_22 at yahoo dot co.uk
2022-06-02 13:29 ` ppalka at gcc dot gnu.org [this message]
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-105752-4-68Xt1CkdGx@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).