public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109480] g++-12 and g++-11 failed to compile the attached source file while g++-10 and clang can. Date: Wed, 12 Apr 2023 05:51:34 +0000 [thread overview] Message-ID: <bug-109480-4-9wEdN3md4s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109480-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109480 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Adding: template <class> friend struct RemoteAccessibleBase; To the RemoteAccessibleBase template struct fixes the issue ....
next prev parent reply other threads:[~2023-04-12 5:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 5:38 [Bug c++/109480] New: " ishikawa at yk dot rim.or.jp 2023-04-12 5:51 ` pinskia at gcc dot gnu.org [this message] 2023-04-12 6:02 ` [Bug c++/109480] [11/12/13 Regression] non-depedent access goes wrong in a template method sometimes pinskia at gcc dot gnu.org 2023-04-12 6:06 ` pinskia at gcc dot gnu.org 2023-04-12 6:55 ` [Bug c++/109480] [11/12/13 Regression] non-depedent access goes wrong in a template method sometimes since r11-1350-g92bed036098928 marxin at gcc dot gnu.org 2023-04-12 10:31 ` rguenth at gcc dot gnu.org 2023-04-12 12:40 ` ppalka at gcc dot gnu.org 2023-05-07 14:29 ` [Bug c++/109480] [11/12/13/14 " cvs-commit at gcc dot gnu.org 2023-05-07 14:30 ` cvs-commit at gcc dot gnu.org 2023-05-07 14:31 ` [Bug c++/109480] [11/12/13 " ppalka at gcc dot gnu.org 2023-05-29 10:08 ` jakub 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-109480-4-9wEdN3md4s@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).