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++/96905] [10/11 Regression] ICE with consteval function: internal compiler error: in cp_gimplify_expr, at cp/cp-gimplify.c:827 Date: Tue, 09 Feb 2021 01:52:45 +0000 [thread overview] Message-ID: <bug-96905-4-6oVq8JT1fx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96905-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96905 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:57d705da0b98f5d398c4b8f9bd76fe8ad98e13bc commit r11-7143-g57d705da0b98f5d398c4b8f9bd76fe8ad98e13bc Author: Jason Merrill <jason@redhat.com> Date: Mon Feb 8 17:16:14 2021 -0500 c++: consteval and explicit instantiation [PR96905] Normally, an explicit instantiation means we want to write out the instantiation. But not for a consteval function. gcc/cp/ChangeLog: PR c++/96905 * pt.c (mark_decl_instantiated): Exit early if consteval. gcc/testsuite/ChangeLog: PR c++/96905 * g++.dg/cpp2a/consteval-expinst1.C: New test.
next prev parent reply other threads:[~2021-02-09 1:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-02 19:23 [Bug c++/96905] New: " redi at gcc dot gnu.org 2020-09-02 20:44 ` [Bug c++/96905] " mpolacek at gcc dot gnu.org 2020-09-02 20:48 ` mpolacek at gcc dot gnu.org 2020-09-02 21:07 ` jakub at gcc dot gnu.org 2020-09-03 10:47 ` [Bug c++/96905] [10/11 Regression] " jakub at gcc dot gnu.org 2020-09-03 19:26 ` jakub at gcc dot gnu.org 2020-10-12 12:25 ` rguenth at gcc dot gnu.org 2021-02-09 1:52 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-11 23:10 ` jason at gcc dot gnu.org 2021-02-12 2:30 ` cvs-commit at gcc dot gnu.org 2021-02-12 2:48 ` 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-96905-4-6oVq8JT1fx@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).