public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "waffl3x at protonmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110566] New: [13/14 Regression] ICE when instantiating function template with template template parameter with 2 or more auto parameters with a dependent member template, ICE in tsubst, at cp/pt.cc:16135
Date: Wed, 05 Jul 2023 21:52:07 +0000	[thread overview]
Message-ID: <bug-110566-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110566
           Summary: [13/14 Regression] ICE when instantiating function
                    template with template template parameter with 2 or
                    more auto parameters with a dependent member template,
                    ICE in tsubst, at cp/pt.cc:16135
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: waffl3x at protonmail dot com
  Target Milestone: ---

https://godbolt.org/z/6d4ec5va3

template<template<auto, auto> typename> void takes_templ();

template<typename>
struct v_v_member_templ_fn {
    template<auto, auto>
    using fn = void;
};

using ice = decltype(takes_templ<v_v_member_templ_fn<void>::template fn>());

This one seems kind of boring to me, only interesting things to note are the
ICE only manifests with 2 or more (I assume) auto template parameters, it works
as expected with only a single auto template parameter.
The version of GCC on my local machine that exhibits this behavior is: 13.1.1
20230429

Not as convoluted as I'm used to, but at least that means it should be easy to
fix! One can hope anyway.

             reply	other threads:[~2023-07-05 21:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 21:52 waffl3x at protonmail dot com [this message]
2023-07-05 22:01 ` [Bug c++/110566] " mpolacek at gcc dot gnu.org
2023-07-06  8:18 ` rguenth at gcc dot gnu.org
2023-07-19 18:45 ` mpolacek at gcc dot gnu.org
2023-07-26 21:22 ` cvs-commit at gcc dot gnu.org
2023-07-26 21:22 ` cvs-commit at gcc dot gnu.org
2023-07-26 21:24 ` [Bug c++/110566] [13 " ppalka at gcc dot gnu.org
2023-07-26 21:47 ` waffl3x at protonmail dot com
2023-07-27  9:27 ` rguenth at gcc dot gnu.org
2023-08-07 23:27 ` cvs-commit at gcc dot gnu.org
2023-08-21 14:09 ` 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-110566-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).