public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108967] internal compiler error: in expand_debug_expr, at cfgexpand.cc:5450
Date: Tue, 28 Feb 2023 14:41:06 +0000 [thread overview]
Message-ID: <bug-108967-4-YZAgvSNwGR@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Status|NEW |ASSIGNED
Keywords| |ice-checking
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
--- gcc/cfgexpand.cc.jj 2023-02-21 11:44:48.479464567 +0100
+++ gcc/cfgexpand.cc 2023-02-28 15:33:09.806750517 +0100
@@ -5365,6 +5365,10 @@ expand_debug_expr (tree exp)
case VEC_WIDEN_MULT_ODD_EXPR:
case VEC_WIDEN_LSHIFT_HI_EXPR:
case VEC_WIDEN_LSHIFT_LO_EXPR:
+ case VEC_WIDEN_PLUS_HI_EXPR:
+ case VEC_WIDEN_PLUS_LO_EXPR:
+ case VEC_WIDEN_MINUS_HI_EXPR:
+ case VEC_WIDEN_MINUS_LO_EXPR:
case VEC_PERM_EXPR:
case VEC_DUPLICATE_EXPR:
case VEC_SERIES_EXPR:
certainly fixes this, not done yet with reduction though (so far at 300KB now).
Haven't bisected yet, but if it reproduces only on the trunk, it would be
latent
since r11-5160-g9fc9573f9a5e9432e53c when those were introduced. Though, it is
an checking ICE only, so doesn't reproduce with release branches by default
(and does the right thing then, the ICE is solely about making sure that new
trees which can be handled in expand_debug_expr are handled there).
next prev parent reply other threads:[~2023-02-28 14:41 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 [this message]
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
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-YZAgvSNwGR@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: link
Be 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).