public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113349] [11/12/13/14 Regression] internal compiler error: in tsubst
Date: Thu, 18 Jan 2024 19:03:09 +0000	[thread overview]
Message-ID: <bug-113349-4-2QqjYs3FD4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113349-4@http.gcc.gnu.org/bugzilla/>

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2
            Summary|internal compiler error: in |[11/12/13/14 Regression]
                   |tsubst                      |internal compiler error: in
                   |                            |tsubst
   Target Milestone|---                         |11.5

--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Before:

error: cannot resolve overloaded function ‘is_same_v’ based on conversion to
type ‘bool’
    9 | static_assert(is_same_v<types<int>::el<1>>);
      |                                            ^

still, a regression.  clang++ accepts the reduced code.

      parent reply	other threads:[~2024-01-18 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12  9:16 [Bug c++/113349] New: " federico at kircheis dot it
2024-01-12  9:28 ` [Bug c++/113349] " pinskia at gcc dot gnu.org
2024-01-18 17:51 ` mpolacek at gcc dot gnu.org
2024-01-18 18:48 ` mpolacek at gcc dot gnu.org
2024-01-18 19:01 ` mpolacek at gcc dot gnu.org
2024-01-18 19:03 ` mpolacek at gcc dot gnu.org [this message]

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-113349-4-2QqjYs3FD4@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).