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++/103994] Module ICE in write_var_def with global variable in global module fragment
Date: Sat, 27 Jan 2024 16:15:16 +0000	[thread overview]
Message-ID: <bug-103994-4-tc8XiqQG0Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103994-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103994

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2024-01-27
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #4 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Reduced testcase exhibiting the latest ICE:

$ cat 103994.H
template <typename> struct TransparentSupport {
  template <typename> using key_arg = int;
};
template <typename Key> struct Map {
  template <typename LookupKey>
  using key_arg = typename TransparentSupport<Key>::template
key_arg<LookupKey>;
};
struct MapKey {
  Map<MapKey> map_;
};

$ g++ -fmodule-header 103994.H
103994.H: internal compiler error: in insert, at cp/module.cc:4924

  parent reply	other threads:[~2024-01-27 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 16:56 [Bug c++/103994] New: Module ICE in mark_by_value, at cp/module.cc:4772 unlvsur at live dot com
2022-10-18 12:59 ` [Bug c++/103994] Module ICE in write_var_def with global variable in global module fragment ppalka at gcc dot gnu.org
2023-02-01 17:33 ` Melven.Roehrig-Zoellner at DLR dot de
2024-01-27 16:10 ` ppalka at gcc dot gnu.org
2024-01-27 16:15 ` ppalka at gcc dot gnu.org [this message]
2024-03-04 16:02 ` ppalka at gcc dot gnu.org
2024-03-07 21:39 ` cvs-commit at gcc dot gnu.org
2024-03-07 21:40 ` 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-103994-4-tc8XiqQG0Q@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).