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++/113814] New: [modules] ICE with imported partial specialization matching existing template-id
Date: Wed, 07 Feb 2024 19:15:05 +0000	[thread overview]
Message-ID: <bug-113814-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113814
           Summary: [modules] ICE with imported partial specialization
                    matching existing template-id
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ppalka at gcc dot gnu.org
  Target Milestone: ---

Reduced from the hello-1 ICE tracked by PR113710:

$ cat header.h
template<int __i, typename _Tp>
struct tuple_element;

template<typename...>
struct tuple { };

template<int __i, typename... _Elements>
tuple_element<__i, tuple<_Elements...>>
get(tuple<_Elements...>);

$ cat testcase.H
#include "header.h"

template<int __i, typename... _Elements>
struct tuple_element<__i, tuple<_Elements...>> { };

$ cat testcase.C
#include "header.h"
import "testcase.H"

int main() {
  get<0>(tuple<int, int>{});
}

$ g++ -fmodules-ts testcase.H testcase.C
testcase.C: In function ‘int main()’:
testcase.C:5:3: internal compiler error: canonical types differ for identical
types ‘tuple_element<__i, tuple<_Elements ...> >’ and ‘tuple_element<__i,
tuple<_Elements ...> >’
    5 |   get<0>(tuple<int, int>{});
      |   ^~~

             reply	other threads:[~2024-02-07 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 19:15 ppalka at gcc dot gnu.org [this message]
2024-02-07 19:25 ` [Bug c++/113814] [modules] canonical types " cvs-commit at gcc dot gnu.org
2024-02-07 19:46 ` mpolacek 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-113814-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).