public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112633] [13/14 Regression] ICE with type aliases and depedent value
Date: Thu, 23 Nov 2023 00:08:18 +0000	[thread overview]
Message-ID: <bug-112633-4-xhX6VK5LKt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112633-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:63c65224e778124eee52acc7b9fcb32cd8ad61e8

commit r13-8090-g63c65224e778124eee52acc7b9fcb32cd8ad61e8
Author: Patrick Palka <ppalka@redhat.com>
Date:   Wed Nov 22 19:07:19 2023 -0500

    c++: alias template of non-template class [PR112633]

    The entering_scope adjustment in tsubst_aggr_type assumes if an alias is
    dependent, then so is the aliased type (and therefore it has template info)
    but that's not true for the dependent alias template specialization ty1<T>
    below which aliases the non-template class A.  In this case no adjustment
    is needed anyway, so we can just punt.

            PR c++/112633

    gcc/cp/ChangeLog:

            * pt.cc (tsubst_aggr_type): Handle empty TYPE_TEMPLATE_INFO
            in the entering_scope adjustment.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/alias-decl-75.C: New test.

    (cherry picked from commit 3f266c84a15d63e42bfad46397fea9aff92b0720)

  parent reply	other threads:[~2023-11-23  0:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  6:27 [Bug c++/112633] New: ICE in parser GCC 13+ (including 14) around type aliases hanicka at hanicka dot net
2023-11-20  6:47 ` [Bug c++/112633] [13/14 Regression] ICE with type aliases and depedent value pinskia at gcc dot gnu.org
2023-11-20  6:47 ` pinskia at gcc dot gnu.org
2023-11-20 14:31 ` ppalka at gcc dot gnu.org
2023-11-22 18:54 ` cvs-commit at gcc dot gnu.org
2023-11-22 19:11 ` hanicka at hanicka dot net
2023-11-23  0:08 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-27 22:19 ` 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-112633-4-xhX6VK5LKt@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).