public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nshead at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114947] New: [modules] ICE when processing class-scope constrained partial specialisations Date: Sun, 05 May 2024 06:05:13 +0000 [thread overview] Message-ID: <bug-114947-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114947 Bug ID: 114947 Summary: [modules] ICE when processing class-scope constrained partial specialisations Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nshead at gcc dot gnu.org Target Milestone: --- The following code ICEs on trunk: // part.cpp module M:part; struct A { template <typename> struct R; template <typename T> requires false struct R<T>; template <typename T> requires true struct R<T>; }; template <typename T> int foo(T, int); template <typename T> int foo(T, A); void go() { foo(0, 0); } // m.cpp export module M; export import :part; This is ultimately because 'set_defining_module' is not called on the partial specialisation declarations of R. This is a regression since r15-101, found while reducing the following testcase that also ICEs even before this change: // a.cpp module; #include <format> export module M:a; // b.cpp module; #include <format> export module M:b; // m.cpp export module M; export import :a; export import :b;
next reply other threads:[~2024-05-05 6:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-05 6:05 nshead at gcc dot gnu.org [this message] 2024-05-24 0:07 ` [Bug c++/114947] " cvs-commit at gcc dot gnu.org 2024-05-24 0:09 ` nshead 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-114947-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).