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++/114795] internal compiler error: in finish_member_declaration after module import in gcc 14.0.1 snapshot Date: Mon, 22 Apr 2024 01:52:19 +0000 [thread overview] Message-ID: <bug-114795-4-FlKZxLwkKp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114795-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114795 Nathaniel Shead <nshead at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=114600, | |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=99000 CC| |nshead at gcc dot gnu.org --- Comment #3 from Nathaniel Shead <nshead at gcc dot gnu.org> --- Similarly to PR114600 (and PR99000 and maybe some others?) this is because we don't support textual redefinitions yet (`#include` after `import` naming the same things). See https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Modules.html: G++’s modules support is not complete. Other than bugs, the known missing pieces are: [...] Textual merging of reachable GM entities Entities may be multiply defined across different header-units. These must be de-duplicated, and this is implemented across imports, or when an import redefines a textually-defined entity. However the reverse is not implemented—textually redefining an entity that has been defined in an imported header-unit. A redefinition error is emitted. A workaround is to ensure that `#include` always goes before `import`, or to use a header module here rather than `#include`. FWIW this particular ICE is because we hit this assertion: /* Don't add decls after definition. */ gcc_assert (TYPE_BEING_DEFINED (current_class_type) /* We can add lambda types when late parsing default arguments. */ || LAMBDA_TYPE_P (TREE_TYPE (decl))); but the class has already been defined earlier, by the import. The other issue here is that we didn't discard the entire GMF here, I suppose possibly because of a similar issue as described in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114630#c2.
next prev parent reply other threads:[~2024-04-22 1:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-21 14:38 [Bug c++/114795] New: " porten at kde dot org 2024-04-21 22:17 ` [Bug c++/114795] " porten at kde dot org 2024-04-22 0:20 ` porten at kde dot org 2024-04-22 1:52 ` nshead at gcc dot gnu.org [this message] 2024-04-22 7:37 ` porten at kde dot org 2024-04-22 8:51 ` nshead at gcc dot gnu.org 2024-04-22 22:49 ` porten at kde dot org 2024-04-23 16:14 ` ppalka at gcc dot gnu.org 2024-04-23 18:01 ` cvs-commit at gcc dot gnu.org 2024-04-23 18:09 ` ppalka at gcc dot gnu.org 2024-04-24 7:15 ` porten at kde dot 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-114795-4-FlKZxLwkKp@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).