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).
