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++/95735] ICE on invalid non-type template argument Date: Thu, 18 Jun 2020 15:51:32 +0000 [thread overview] Message-ID: <bug-95735-4-wrr9jyRGOb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95735-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95735 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:5421fae8b17c7401f3a4ac5b9f414a47f7bda379 commit r11-1516-g5421fae8b17c7401f3a4ac5b9f414a47f7bda379 Author: Marek Polacek <polacek@redhat.com> Date: Thu Jun 18 09:38:42 2020 -0400 c++: ICE in requires-expressions with invalid args [PR95735] This ICE-on-invalid goes back to GCC 6. In finish_template_variable, if coerce_innermost_template_parms returns error_mark_node, we pass it down to constraints_satisfied_p and that error_mark_node flows down to various satisfy_* functions and then to various tsubst_* functions, where we crash. diagnose_constraints also doesn't cope with error arglist, so I think we should just return as in the patch below. gcc/cp/ChangeLog: PR c++/95735 * pt.c (finish_template_variable): Return if coerce_innermost_template_parms return error_mark_node. gcc/testsuite/ChangeLog: PR c++/95735 * g++.dg/cpp2a/concepts-err2.C: New test.
next prev parent reply other threads:[~2020-06-18 15:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-18 6:09 [Bug c++/95735] New: " johelegp at gmail dot com 2020-06-18 7:40 ` [Bug c++/95735] " marxin at gcc dot gnu.org 2020-06-18 13:33 ` mpolacek at gcc dot gnu.org 2020-06-18 15:11 ` mpolacek at gcc dot gnu.org 2020-06-18 15:51 ` cvs-commit at gcc dot gnu.org [this message] 2020-06-18 15:52 ` mpolacek 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-95735-4-wrr9jyRGOb@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).