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++/104107] [10 Regression] parsing crashes on class template instantiation since r9-6853-g17838af989014f5e Date: Wed, 15 Mar 2023 12:45:16 +0000 [thread overview] Message-ID: <bug-104107-4-X2doNjAP3p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104107-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104107 --- Comment #10 from CVS 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:3ea64aad06a2b32739028bae03b9b9a5691d2d30 commit r13-6693-g3ea64aad06a2b32739028bae03b9b9a5691d2d30 Author: Jason Merrill <jason@redhat.com> Date: Fri Mar 10 14:55:27 2023 -0500 c++: passing one ttp to another [PR108179] I kept trying to improve our choice of how many levels of outer_args to add, when really the problem was that outer_args are for PARM and for this reverse deduction we should be adding the outer arguments for ARG. I spent quite a while trying to get DECL_CONTEXT set consistently on template template parameters that have gone through reduce_template_parm_level before I realized I could just use current_scope(). PR c++/108179 PR c++/104107 PR c++/95036 gcc/cp/ChangeLog: * pt.cc (coerce_template_template_parms): Use args from DECL_CONTEXT (arg_tmpl) instead of outer_args. gcc/testsuite/ChangeLog: * g++.dg/template/ttp35.C: New test.
next prev parent reply other threads:[~2023-03-15 12:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 0:01 [Bug c++/104107] New: parsing crashes on class template instantiation gzoumix at hotmail dot com 2022-01-19 0:14 ` [Bug c++/104107] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-19 0:30 ` pinskia at gcc dot gnu.org 2022-01-19 0:31 ` pinskia at gcc dot gnu.org 2022-01-19 10:57 ` rguenth at gcc dot gnu.org 2022-01-31 15:11 ` [Bug c++/104107] [9/10/11/12 Regression] parsing crashes on class template instantiation since r9-6853-g17838af989014f5e marxin at gcc dot gnu.org 2022-02-10 22:55 ` jason at gcc dot gnu.org 2022-02-15 5:06 ` cvs-commit at gcc dot gnu.org 2022-02-16 0:12 ` [Bug c++/104107] [9/10/11 " jason at gcc dot gnu.org 2022-03-28 19:13 ` cvs-commit at gcc dot gnu.org 2022-03-28 19:13 ` [Bug c++/104107] [9/10 " jason at gcc dot gnu.org 2022-05-27 9:47 ` [Bug c++/104107] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:47 ` jakub at gcc dot gnu.org 2023-03-15 12:45 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-07 9:49 ` rguenth 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-104107-4-X2doNjAP3p@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).