public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105761] [11/12/13 Regression] ICE on hidden friend definition defined in base type since r11-388-gc4bff4c230c8d341 Date: Fri, 03 Jun 2022 17:44:52 +0000 [thread overview] Message-ID: <bug-105761-4-c9tcAIqBNq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105761-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105761 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:284ae8b46f5eef74c0b660a87a7169497f559e73 commit r13-985-g284ae8b46f5eef74c0b660a87a7169497f559e73 Author: Jason Merrill <jason@redhat.com> Date: Fri Jun 3 12:35:12 2022 -0400 c++: redeclared hidden friend [PR105761] Here, when we see the second declaration of f we match it with the first one, copy over DECL_TEMPLATE_INFO, and then try to use it when parsing the definition, leading to confusion. PR c++/105761 gcc/cp/ChangeLog: * decl.cc (duplicate_decls): Don't copy DECL_TEMPLATE_INFO from a hidden friend. gcc/testsuite/ChangeLog: * g++.dg/cpp1y/auto-fn64.C: New test.
next prev parent reply other threads:[~2022-06-03 17:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-28 16:56 [Bug c++/105761] New: ICE on hidden friend definition defined in base type johelegp at gmail dot com 2022-05-28 18:15 ` [Bug c++/105761] " johelegp at gmail dot com 2022-05-30 10:04 ` [Bug c++/105761] [11/12/13 Regression] ICE on hidden friend definition defined in base type since r11-388-gc4bff4c230c8d341 marxin at gcc dot gnu.org 2022-06-03 16:27 ` jason at gcc dot gnu.org 2022-06-03 17:44 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-03 18:12 ` cvs-commit at gcc dot gnu.org 2022-06-03 18:42 ` cvs-commit at gcc dot gnu.org 2022-06-03 18:43 ` jason at gcc dot gnu.org 2022-06-08 20:38 ` cvs-commit at gcc dot gnu.org 2022-06-08 21:31 ` cvs-commit at gcc dot gnu.org 2022-06-08 21:31 ` cvs-commit 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-105761-4-c9tcAIqBNq@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).