public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98718] New: [modules] use of partitions causes ICE in write_macro_maps
Date: Mon, 18 Jan 2021 07:37:43 +0000 [thread overview]
Message-ID: <bug-98718-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98718
Bug ID: 98718
Summary: [modules] use of partitions causes ICE in
write_macro_maps
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: boris at kolpackov dot net
Target Milestone: ---
Created attachment 49988
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49988&action=edit
Reproducer
The attached set of translation units causes an internal compiler error:
hello.mxx:5:9: internal compiler error: in write_macro_maps, at
cp/module.cc:16113
5 | export module hello;
| ^~~~~~
0xc60a67 module_state::write_macro_maps(elf_out*, location_map_info&,
module_state_config*, unsigned int*)
../../gcc/gcc/cp/module.cc:16113
0xc659f1 module_state::write(elf_out*, cpp_reader*)
../../gcc/gcc/cp/module.cc:17727
0xc6bbfd finish_module_processing(cpp_reader*)
../../gcc/gcc/cp/module.cc:19747
0xb8a7a1 c_parse_final_cleanups()
../../gcc/gcc/cp/decl2.c:5178
0xf0b805 c_common_parse_file()
../../gcc/gcc/c-family/c-opts.c:1233
If I replace std::string with const char* and get rid of the <string>
inclusion, then the ICE disappears. The build transcript is included in the
attached archive.
next reply other threads:[~2021-01-18 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 7:37 boris at kolpackov dot net [this message]
2021-01-18 8:43 ` [Bug c++/98718] " boris at kolpackov dot net
2021-02-22 15:40 ` nathan at gcc dot gnu.org
2021-02-23 18:26 ` nathan at gcc dot gnu.org
2021-02-24 20:46 ` cvs-commit at gcc dot gnu.org
2021-02-24 20:47 ` nathan at gcc dot gnu.org
2021-02-26 12:49 ` nathan at gcc dot gnu.org
2021-02-26 12:49 ` nathan at gcc dot gnu.org
2021-03-04 7:08 ` boris at kolpackov dot net
2021-03-05 18:19 ` 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-98718-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: link
Be 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).