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++/97740] [10/11/12/13 Regression] Weird error message about accessing a private member of my own class inside of std::string_view inside of constexpr Date: Fri, 24 Mar 2023 16:08:25 +0000 [thread overview] Message-ID: <bug-97740-4-LqhzjqNPfJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97740-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97740 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |10.5 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=96716 Summary|Weird error message about |[10/11/12/13 Regression] |accessing a private member |Weird error message about |of my own class inside of |accessing a private member |std::string_view inside of |of my own class inside of |constexpr |std::string_view inside of | |constexpr CC| |jason at gcc dot gnu.org, | |ppalka at gcc dot gnu.org --- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> --- Here's a reduced C++11 testcase that became rejects-valid after r10-6416-g8fda2c274ac66d: struct A { constexpr const int* get() const { return &m; } private: int m = 42; } a; struct B { const int* p; }; template<class> void f() { constexpr B b = {a.get()}; } template void f<int>(); <stdin>: In function ‘void f()’: <stdin>:11:25: error: ‘int A::m’ is private within this context <stdin>:4:7: note: declared private here <stdin>: In instantiation of ‘void f() [with <template-parameter-1-1> = int]’: <stdin>:14:22: required from here <stdin>:11:25: error: ‘int A::m’ is private within this context <stdin>:4:7: note: declared private here
next prev parent reply other threads:[~2023-03-24 16:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-06 9:03 [Bug c++/97740] New: " markus.boeck02 at gmail dot com 2020-11-09 15:31 ` [Bug c++/97740] " redi at gcc dot gnu.org 2020-11-09 15:32 ` redi at gcc dot gnu.org 2021-08-28 22:16 ` pinskia at gcc dot gnu.org 2023-03-24 16:08 ` ppalka at gcc dot gnu.org [this message] 2023-03-24 16:10 ` [Bug c++/97740] [10/11/12/13 Regression] " ppalka at gcc dot gnu.org 2023-07-07 10:38 ` [Bug c++/97740] [11/12/13/14 " 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-97740-4-LqhzjqNPfJ@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).