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++/99528] [modules] ICE with iostream& vector Date: Thu, 11 Mar 2021 17:50:06 +0000 [thread overview] Message-ID: <bug-99528-4-ohMzwdkNiN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99528-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99528 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>: https://gcc.gnu.org/g:edc61d34eb4212d5547e9f628b5f7f4d15ee0060 commit r11-7626-gedc61d34eb4212d5547e9f628b5f7f4d15ee0060 Author: Nathan Sidwell <nathan@acm.org> Date: Thu Mar 11 05:39:11 2021 -0800 c++: template partial instantiation mismatch [PR 99528] This turned out to be an existing problem, which had been hidden by other bugs. Templated members of templated classes can end up instantiating the template itself, and we were not handling the mergeableness of that correctly. PR c++/99528 gcc/cp/ * module.cc (enum merge_kind): Delete MK_type_tmpl_spec, MK_decl_tmpl_spec. (trees_in::decl_value): Adjust add_mergeable_specialization call. (trees_out::get_merge_kind): Adjust detecting a partial template instantiation. (trees_out::key_mergeable): Adjust handling same. (trees_in::key_mergeabvle): Likewise. gcc/testsuite/ * g++.dg/modules/pr99528.h: New. * g++.dg/modules/pr99528_a.H: New. * g++.dg/modules/pr99528_b.H: New. * g++.dg/modules/pr99528_c.C: New.
next prev parent reply other threads:[~2021-03-11 17:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 20:39 [Bug c++/99528] New: " nathan at gcc dot gnu.org 2021-03-10 20:39 ` [Bug c++/99528] " nathan at gcc dot gnu.org 2021-03-10 21:12 ` nathan at gcc dot gnu.org 2021-03-11 17:50 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-11 17:50 ` nathan at gcc dot gnu.org 2021-03-15 12:42 ` nathan 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-99528-4-ohMzwdkNiN@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).