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++/109899] [12/13 Regression] ICE in check_noexcept_r, at cp/except.cc:1065 Date: Mon, 15 Jan 2024 23:08:51 +0000 [thread overview] Message-ID: <bug-109899-4-nAhmaTl9bN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109899-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:6477b3b9c3e5be5dfe549dcb7b3cef2b49e3690c commit r12-10098-g6477b3b9c3e5be5dfe549dcb7b3cef2b49e3690c Author: Patrick Palka <ppalka@redhat.com> Date: Mon Jan 15 16:49:19 2024 -0500 c++: non-dep array list-init w/ non-triv dtor [PR109899] The get_target_expr call added in r12-7069-g119cea98f66476 causes us for the below testcase to call build_vec_delete in a template context, which builds a templated destructor call and checks expr_noexcept_p for it, which ICEs because the call has templated form. Much of the work of build_vec_delete however is code generation and thus will just get discarded in a template context, and that includes the code guarded by expr_noexcept_p. So this patch narrowly fixes this ICE by eliding the expr_noexcept_p call when in a template context. PR c++/109899 gcc/cp/ChangeLog: * init.cc (build_vec_delete_1): Assume expr_noexcept_p returns false in a template context. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/initlist-array21.C: New test. Reviewed-by: Jason Merrill <jason@redhat.com> (cherry picked from commit d33c3b5ac9b9b3e314ae9118d483ade7e91a80a5)
next prev parent reply other threads:[~2024-01-15 23:08 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-17 21:16 [Bug c++/109899] New: " jeanmichael.celerier at gmail dot com 2023-05-17 21:20 ` [Bug c++/109899] " pinskia at gcc dot gnu.org 2023-05-17 22:38 ` [Bug c++/109899] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-05-17 22:42 ` pinskia at gcc dot gnu.org 2023-05-18 6:23 ` rguenth at gcc dot gnu.org 2023-05-18 13:23 ` mpolacek at gcc dot gnu.org 2023-05-18 13:25 ` mpolacek at gcc dot gnu.org 2023-07-26 5:31 ` pinskia at gcc dot gnu.org 2023-07-26 5:32 ` pinskia at gcc dot gnu.org 2024-01-05 23:34 ` lozko.roma at gmail dot com 2024-01-15 21:50 ` cvs-commit at gcc dot gnu.org 2024-01-15 21:52 ` [Bug c++/109899] [12/13 " ppalka at gcc dot gnu.org 2024-01-15 21:52 ` ppalka at gcc dot gnu.org 2024-01-15 22:34 ` cvs-commit at gcc dot gnu.org 2024-01-15 23:08 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-15 23:09 ` ppalka 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-109899-4-nAhmaTl9bN@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).