public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105912] internal compiler error: in extract_call_expr, at cp/call.cc:7114
Date: Thu, 09 Jun 2022 20:38:55 +0000	[thread overview]
Message-ID: <bug-105912-4-ZJqqLgUtXH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105912-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Luke Dalessandro <ldalessandro at gmail dot com> ---
Somewhat reduced testcase:

    template <wchar_t> struct A {};
    template <wchar_t> struct B {};

    template <wchar_t a>
    static consteval auto operator~(A<a>) -> B<a> {
        return {};
    }

    A<'i'> i;

    template <class>
    auto test() -> bool {
        auto ii = ~i;      // ICE HERE
        return true;
    }

    int main()
    {
        bool i = test<int>();
    }

https://godbolt.org/z/rEf4neexc

  reply	other threads:[~2022-06-09 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 20:28 [Bug c++/105912] New: " ldalessandro at gmail dot com
2022-06-09 20:38 ` ldalessandro at gmail dot com [this message]
2022-06-09 20:42 ` [Bug c++/105912] " mpolacek at gcc dot gnu.org
2022-06-09 21:02 ` mpolacek at gcc dot gnu.org
2022-06-16 13:12 ` marxin at gcc dot gnu.org
2022-07-12 13:48 ` ppalka at gcc dot gnu.org
2022-07-13 18:03 ` cvs-commit at gcc dot gnu.org
2022-07-13 18:05 ` ppalka at gcc dot gnu.org
2022-07-21 18:38 ` cvs-commit at gcc dot gnu.org
2022-07-21 18:39 ` 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-105912-4-ZJqqLgUtXH@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).