public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103921] [modules] ICE dependent expression in explicit-specifier of instantiation of imported template
Date: Wed, 05 Jan 2022 18:15:23 +0000	[thread overview]
Message-ID: <bug-103921-4-p5Ok9Dl5cp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103921-4@http.gcc.gnu.org/bugzilla/>

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

Johel Ernesto Guerrero Peña <johelegp at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[modules] ICE requires in   |[modules] ICE dependent
                   |explicit-specifier of       |expression in
                   |instantiation of imported   |explicit-specifier of
                   |template                    |instantiation of imported
                   |                            |template

--- Comment #2 from Johel Ernesto Guerrero Peña <johelegp at gmail dot com> ---
It actually ICEs whenever the expression is dependent:
https://godbolt.org/z/oqbnanoex.

mod.cpp:
```C++
export module mod;

template<class> constexpr bool b{true};

export template<class N> struct quantity {
  template<class N2>
  explicit(b<N>) operator quantity<N2>() const;
};
```

  parent reply	other threads:[~2022-01-05 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 16:52 [Bug c++/103921] New: [modules] ICE requires " johelegp at gmail dot com
2022-01-05 17:01 ` [Bug c++/103921] " johelegp at gmail dot com
2022-01-05 18:15 ` johelegp at gmail dot com [this message]
2022-01-05 18:25 ` [Bug c++/103921] [modules] ICE dependent expression " johelegp at gmail dot com
2022-01-05 18:27 ` johelegp at gmail dot com
2022-02-09 16:32 ` johelegp at gmail dot com

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-103921-4-p5Ok9Dl5cp@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).