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++/114114] [11/12/13/14 Regression] Internal compiler error on function-local conditional noexcept Date: Wed, 06 Mar 2024 16:47:34 +0000 [thread overview] Message-ID: <bug-114114-4-GPGMoGQEEq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114114-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114114 --- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:dc6c3bfb59baab28b998e18396c06087b6d9b0ed commit r14-9339-gdc6c3bfb59baab28b998e18396c06087b6d9b0ed Author: Marek Polacek <polacek@redhat.com> Date: Tue Mar 5 13:33:10 2024 -0500 c++: ICE with noexcept and local specialization [PR114114] Here we ICE because we call register_local_specialization while local_specializations is null, so local_specializations->put (); crashes on null this. It's null since maybe_instantiate_noexcept calls push_to_top_level which creates a new scope. Normally, I would have guessed that we need a new local_specialization_stack. But here we're dealing with an operand of a noexcept, which is an unevaluated operand, and those aren't registered in the hash map. maybe_instantiate_noexcept wasn't signalling that it's substituting an unevaluated operand though. PR c++/114114 gcc/cp/ChangeLog: * pt.cc (maybe_instantiate_noexcept): Save/restore cp_unevaluated_operand, c_inhibit_evaluation_warnings, and cp_noexcept_operand around the tsubst_expr call. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/noexcept84.C: New test.
next prev parent reply other threads:[~2024-03-06 16:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-26 13:46 [Bug c++/114114] New: " yves.bailly at hexagon dot com 2024-02-26 16:58 ` [Bug c++/114114] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2024-02-26 17:01 ` pinskia at gcc dot gnu.org 2024-02-26 19:01 ` ppalka at gcc dot gnu.org 2024-02-27 8:24 ` yves.bailly at hexagon dot com 2024-03-04 18:21 ` mpolacek at gcc dot gnu.org 2024-03-06 16:47 ` cvs-commit at gcc dot gnu.org [this message] 2024-03-06 16:48 ` [Bug c++/114114] [11/12/13 " 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-114114-4-GPGMoGQEEq@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).