public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111785] [modules] ICE when compiling fmt lib as module
Date: Tue, 24 Oct 2023 00:48:56 +0000 [thread overview]
Message-ID: <bug-111785-4-scvaR1EiGM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111785-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111785
--- Comment #5 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Luis Caro Campos from comment #2)
> Thanks Patrick for looking into this. I think your message got cut off?
>
> I've removed the calls to the GCC optimize pragmas, and still get an ICE:
>
> src/fmt.cc:71:8: internal compiler error: in insert, at cp/module.cc:4920
> 71 | export module fmt;
> | ^
> 0x9a371f trees_out::insert(tree_node*, walk_kind)
> ../../gcc/cp/module.cc:4920
> 0x9a6e37 trees_out::decl_node(tree_nod
>
>
> This time the error references a different line of the same module.cc file,
> in case that is relevant.
Hopefully this ICE is gone after the PR105322 fix r14-4806?
next prev parent reply other threads:[~2023-10-24 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 13:15 [Bug c++/111785] New: " mends-sputter.0z at icloud dot com
2023-10-16 19:11 ` [Bug c++/111785] " ppalka at gcc dot gnu.org
2023-10-17 17:00 ` mends-sputter.0z at icloud dot com
2023-10-17 17:09 ` mends-sputter.0z at icloud dot com
2023-10-17 18:44 ` ppalka at gcc dot gnu.org
2023-10-24 0:48 ` ppalka at gcc dot gnu.org [this message]
2024-03-06 21:35 ` ppalka 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-111785-4-scvaR1EiGM@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).