public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109859] [12/13/14 Regression] ICE on concept mis-typed as template type parameter Date: Fri, 16 Feb 2024 18:54:22 +0000 [thread overview] Message-ID: <bug-109859-4-dPKNXWaEHb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109859-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109859 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org --- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> --- We're hitting the assert here: /* In a template parameter list, a type-parameter can be introduced by type-constraints alone. */ if (processing_template_parmlist && !placeholder) { /* In a default argument we may not be creating new parameters. */ if (parser->local_variables_forbidden_p & LOCAL_VARS_FORBIDDEN) { /* If this assert turns out to be false, do error() instead. */ gcc_assert (tentative); return error_mark_node; } so presumably we should change it to error() as the comment says.
prev parent reply other threads:[~2024-02-16 18:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-15 8:53 [Bug c++/109859] New: " saifi.khan at nishan dot io 2023-05-15 9:22 ` [Bug c++/109859] " hewillk at gmail dot com 2023-05-15 14:47 ` [Bug c++/109859] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-15 14:47 ` pinskia at gcc dot gnu.org 2023-05-17 6:44 ` rguenth at gcc dot gnu.org 2023-08-29 5:53 ` pinskia at gcc dot gnu.org 2024-02-16 18:54 ` mpolacek at gcc dot gnu.org [this message]
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-109859-4-dPKNXWaEHb@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).