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++/100634] [11/12 Regression] ICE in convert_nontype_argument, at cp/pt.c:7653 Date: Thu, 20 May 2021 03:12:57 +0000 [thread overview] Message-ID: <bug-100634-4-ExVDCxNGQv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100634-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100634 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:b54e50285c716fabc3980c5383c4898018a60b28 commit r11-8444-gb54e50285c716fabc3980c5383c4898018a60b28 Author: Jason Merrill <jason@redhat.com> Date: Wed May 19 17:33:21 2021 -0400 c++: _Complex template parameter [PR100634] We were crashing because invalid_nontype_parm_type_p allowed _Complex template parms, but convert_nontype_argument didn't know what to do for them. Let's just disallow it, people can and should use std::complex instead. PR c++/100634 gcc/cp/ChangeLog: * pt.c (invalid_nontype_parm_type_p): Return true for COMPLEX_TYPE. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/nontype-complex1.C: New test.
next prev parent reply other threads:[~2021-05-20 3:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-17 6:48 [Bug c++/100634] New: " asolokha at gmx dot com 2021-05-17 8:12 ` [Bug c++/100634] " marxin at gcc dot gnu.org 2021-05-17 8:59 ` jakub at gcc dot gnu.org 2021-05-17 12:52 ` rguenth at gcc dot gnu.org 2021-05-19 21:30 ` jason at gcc dot gnu.org 2021-05-20 3:11 ` cvs-commit at gcc dot gnu.org 2021-05-20 3:12 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-20 3:13 ` jason 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-100634-4-ExVDCxNGQv@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).