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 debug/108967] [11 Regression] internal compiler error: in expand_debug_expr, at cfgexpand.cc:5450 Date: Tue, 02 May 2023 20:15:11 +0000 [thread overview] Message-ID: <bug-108967-4-KePCa22L60@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108967-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108967 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:54b240621d372e63d8fcacae591e39b36634ac18 commit r11-10717-g54b240621d372e63d8fcacae591e39b36634ac18 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Mar 1 10:26:46 2023 +0100 cfgexpand: Handle WIDEN_{PLUS,MINUS}_EXPR and VEC_WIDEN_{PLUS,MINUS}_{HI,LO}_EXPR in expand_debug_expr [PR108967] When these tree codes were introduced, expand_debug_expr hasn't been updated to handle them. For the VEC_*_EXPR we currently mostly punt, the non-vector ones can be handled easily. In release compilers this doesn't ICE, but with checking we ICE so that we make sure to handle all the needed tree codes there. 2023-03-01 Jakub Jelinek <jakub@redhat.com> PR debug/108967 * cfgexpand.c (expand_debug_expr): Handle WIDEN_{PLUS,MINUS}_EXPR and VEC_WIDEN_{PLUS,MINUS}_{HI,LO}_EXPR. * g++.dg/debug/pr108967.C: New test. (cherry picked from commit 520403f324a6ed8b527f39239709dd0841b992e2)
next prev parent reply other threads:[~2023-05-02 20:15 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 12:14 [Bug c++/108967] New: " malat at debian dot org 2023-02-28 13:00 ` [Bug c++/108967] " jakub at gcc dot gnu.org 2023-02-28 13:52 ` ktkachov at gcc dot gnu.org 2023-02-28 14:41 ` jakub at gcc dot gnu.org 2023-02-28 15:38 ` jakub at gcc dot gnu.org 2023-02-28 16:52 ` [Bug debug/108967] " jakub at gcc dot gnu.org 2023-03-01 9:27 ` cvs-commit at gcc dot gnu.org 2023-03-01 9:33 ` [Bug debug/108967] [11/12 Regression] " jakub at gcc dot gnu.org 2023-03-19 5:30 ` cvs-commit at gcc dot gnu.org 2023-03-20 10:27 ` [Bug debug/108967] [11 " jakub at gcc dot gnu.org 2023-04-26 6:57 ` rguenth at gcc dot gnu.org 2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-03 10:41 ` jakub 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-108967-4-KePCa22L60@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).