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++/114377] [13 Regression] GCC crashes on an example of CTAD for alias templates Date: Wed, 01 May 2024 20:31:54 +0000 [thread overview] Message-ID: <bug-114377-4-tRoSyUlL7X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114377-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114377 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:60e1e13f458f1fcfb05a30ace57fa682461e2732 commit r13-8669-g60e1e13f458f1fcfb05a30ace57fa682461e2732 Author: centurion <centurion009@proton.me> Date: Wed Mar 27 18:36:37 2024 +0000 c++: alias CTAD and template template parm [PR114377] To match all the other places that pull a _TEMPLATE_PARM out of a _DECL (get_template_parm_index, etc.). This change is too small to be legally significant for copyright. PR c++/114377 gcc/cp/ChangeLog: * pt.cc (find_template_parameter_info::found): Use TREE_TYPE for TEMPLATE_DECL instead of DECL_INITIAL. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/class-deduction-alias19.C: New test. Reviewed-by: Jason Merrill <jason@redhat.com> (cherry picked from commit 801e82acd6b4f0cf863529875947e394899ea7b9)
next prev parent reply other threads:[~2024-05-01 20:31 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-18 13:18 [Bug c++/114377] New: " hokein.wu at gmail dot com 2024-03-18 14:07 ` [Bug c++/114377] [13/14 Regression] " ppalka at gcc dot gnu.org 2024-03-22 13:30 ` law at gcc dot gnu.org 2024-03-25 12:53 ` rguenth at gcc dot gnu.org 2024-03-27 14:05 ` ppalka at gcc dot gnu.org 2024-03-27 14:20 ` ppalka at gcc dot gnu.org 2024-04-04 21:19 ` cvs-commit at gcc dot gnu.org 2024-05-01 20:31 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-01 20:41 ` [Bug c++/114377] [13 " jason 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-114377-4-tRoSyUlL7X@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: linkBe 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).