public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114393] [14 regression] over eager "invalid use of void expression" ? Date: Tue, 19 Mar 2024 11:32:52 +0000 [thread overview] Message-ID: <bug-114393-4-AXrL7LFthK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114393-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114393 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2024-03-19 CC| |ppalka at gcc dot gnu.org --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- r14-2170 started to reject it Author: Patrick Palka Date: Wed Jun 28 20:43:33 2023 c++: ahead of time variable template-id coercion [PR89442] This patch makes us coerce the arguments of a variable template-id ahead of time, as we do for class template-ids, which causes us to immediately diagnose template parm/arg kind mismatches and arity mismatches. Unfortunately this causes a regression in cpp1z/constexpr-if20.C: coercing the variable template-id m<ar, as> ahead of time means we strip it of typedefs, yielding m<typename C<i>::q, typename C<j>::q>, but in this stripped form we're directly using 'i' and so we expect to have captured it. This is a variable template version of PR107437. PR c++/89442 PR c++/107437 gcc/cp/ChangeLog: * cp-tree.h (lookup_template_variable): Add complain parameter. * parser.cc (cp_parser_template_id): Pass tf_warning_or_error to lookup_template_variable. * pt.cc (lookup_template_variable): Add complain parameter. Coerce template arguments here ... (finish_template_variable): ... instead of here. (lookup_and_finish_template_variable): Check for error_mark_node result from lookup_template_variable. (tsubst_copy) <case TEMPLATE_ID_EXPR>: Pass complain to lookup_template_variable. (instantiate_template): Use build2 instead of lookup_template_variable to build a TEMPLATE_ID_EXPR for most_specialized_partial_spec.
next prev parent reply other threads:[~2024-03-19 11:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-19 11:09 [Bug c++/114393] New: " prlw1 at cam dot ac.uk 2024-03-19 11:29 ` [Bug c++/114393] [14 regression] " redi at gcc dot gnu.org 2024-03-19 11:32 ` redi at gcc dot gnu.org [this message] 2024-03-19 11:56 ` [Bug c++/114393] [14 regression] over eager "invalid use of void expression" ? since r14-2170-g4cf64d9cc2faf4 rguenth at gcc dot gnu.org 2024-03-19 22:42 ` pinskia at gcc dot gnu.org 2024-03-20 3:51 ` pinskia at gcc dot gnu.org 2024-03-20 4:04 ` pinskia at gcc dot gnu.org 2024-03-25 19:05 ` ppalka at gcc dot gnu.org 2024-03-29 23:49 ` law at gcc dot gnu.org 2024-04-12 19:08 ` ppalka at gcc dot gnu.org 2024-04-12 19:09 ` ppalka at gcc dot gnu.org 2024-04-12 19:11 ` ppalka at gcc dot gnu.org 2024-04-14 19:27 ` prlw1 at cam dot ac.uk
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-114393-4-AXrL7LFthK@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).