public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102156] New: `cannot call constructor` error during member access Date: Wed, 01 Sep 2021 07:30:45 +0000 [thread overview] Message-ID: <bug-102156-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102156 Bug ID: 102156 Summary: `cannot call constructor` error during member access Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- The following valid code accesses a field in a base class: ``` struct A { int v; }; template <typename T> struct B : T {}; struct C : B<A> {}; int main() { return C{}.B::B<A>::v; } ``` but GCC prints an error: ``` cannot call constructor 'B<A>::B' directly ``` https://gcc.godbolt.org/z/hchqG7Tq8
next reply other threads:[~2021-09-01 7:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-01 7:30 fchelnokov at gmail dot com [this message] 2021-09-01 8:00 ` [Bug c++/102156] " pinskia at gcc dot gnu.org 2021-09-01 8:09 ` [Bug c++/102156] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-17 13:51 ` rguenth at gcc dot gnu.org 2022-04-15 4:36 ` jason 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-102156-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).