public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ed at catmur dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109677] New: Access control bypass for function template default argument brace initialization of private default constructor Date: Sat, 29 Apr 2023 01:49:39 +0000 [thread overview] Message-ID: <bug-109677-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109677 Bug ID: 109677 Summary: Access control bypass for function template default argument brace initialization of private default constructor Product: gcc Version: 13.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ed at catmur dot uk Target Milestone: --- gcc accepts-invalid: struct B { private: B(); }; template<class T> int f(T = {}); int i = f<B>(); This is mostly a curiosity, but it came up while trying to understand why a misuse of the passkey pattern was seemingly working.
next reply other threads:[~2023-04-29 1:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-29 1:49 ed at catmur dot uk [this message] 2023-04-29 2:31 ` [Bug c++/109677] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-01 12:10 ` ppalka at gcc dot gnu.org 2023-05-29 10:08 ` jakub at gcc dot gnu.org 2024-01-12 10:39 ` rguenth 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-109677-4@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).