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++/100055] [10/11/12 Regression] ICE on invalid requires expression Date: Mon, 03 May 2021 16:48:29 +0000 [thread overview] Message-ID: <bug-100055-4-5miL8WWxtS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100055-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100055 --- Comment #5 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:c9b6890d0b6aa030b307fdb620f8c53ed59ca3b5 commit r12-389-gc9b6890d0b6aa030b307fdb620f8c53ed59ca3b5 Author: Marek Polacek <polacek@redhat.com> Date: Thu Apr 22 17:32:01 2021 -0400 c++: Fix ICE with invalid requires-expression [PR100055] This fixes a crash on invalid requires-expression: in this test, current_template_parms is null so accessing TEMPLATE_PARMS_CONSTRAINTS is going to fail. So don't crash, but make sure we've complained already. gcc/cp/ChangeLog: PR c++/100055 * decl.c (grokfndecl): Check current_template_parms. gcc/testsuite/ChangeLog: PR c++/100055 * g++.dg/concepts/diagnostic18.C: New test.
next prev parent reply other threads:[~2021-05-03 16:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-12 23:10 [Bug c++/100055] New: " ldalessandro at gmail dot com 2021-04-22 16:35 ` [Bug c++/100055] " mpolacek at gcc dot gnu.org 2021-04-22 16:41 ` [Bug c++/100055] [10/11/12 Regression] " mpolacek at gcc dot gnu.org 2021-04-22 17:32 ` hewillk at gmail dot com 2021-04-26 14:51 ` mpolacek at gcc dot gnu.org 2021-05-03 16:48 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-03 16:49 ` mpolacek at gcc dot gnu.org 2021-11-12 21:23 ` pinskia at gcc dot gnu.org 2022-01-04 2:23 ` pinskia at gcc dot gnu.org 2022-01-04 2:24 ` pinskia at gcc dot gnu.org 2022-01-04 2:26 ` pinskia 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-100055-4-5miL8WWxtS@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).