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++/113498] [14 regression] ICE in GCC trunk: tree check: have using_decl in get_template_info, at cp/pt.cc:357 since r14-6064 Date: Fri, 19 Jan 2024 19:23:36 +0000 [thread overview] Message-ID: <bug-113498-4-NUs7aoYWfc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113498-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113498 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:1338ad23ff3c1e4f552cdb64e36cef12eda2e050 commit r14-8294-g1338ad23ff3c1e4f552cdb64e36cef12eda2e050 Author: Jason Merrill <jason@redhat.com> Date: Fri Jan 19 13:11:05 2024 -0500 c++: requires and using-decl [PR113498] get_template_info was crashing because it assumed that any decl with DECL_LANG_SPECIFIC could use DECL_TEMPLATE_INFO. It's more complicated than that. PR c++/113498 gcc/cp/ChangeLog: * pt.cc (decl_template_info): New fn. (get_template_info): Use it. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-using4.C: New test.
next prev parent reply other threads:[~2024-01-19 19:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 6:35 [Bug c++/113498] New: ICE in GCC trunk: tree check: have using_decl in get_template_info, at cp/pt.cc:357 bobmiller at nvidia dot com 2024-01-19 6:44 ` [Bug c++/113498] " bobmiller at nvidia dot com 2024-01-19 7:58 ` bobmiller at nvidia dot com 2024-01-19 9:19 ` [Bug c++/113498] [14 regression] " rguenth at gcc dot gnu.org 2024-01-19 16:15 ` [Bug c++/113498] [14 regression] ICE in GCC trunk: tree check: have using_decl in get_template_info, at cp/pt.cc:357 since r14-6064 jakub at gcc dot gnu.org 2024-01-19 17:01 ` jason at gcc dot gnu.org 2024-01-19 19:23 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-19 19:24 ` 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-113498-4-NUs7aoYWfc@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).