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 middle-end/108237] [13 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:281 at -O since r13-1085-g90467f0ad649d081
Date: Tue, 03 Jan 2023 16:35:03 +0000 [thread overview]
Message-ID: <bug-108237-4-rbcsMtka6q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108237-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108237
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ah, I see, it is forwprop4 which does that:
+Applying pattern match.pd:6223, generic-match.cc:75158
...
- _15 = v.2_7 & { 18446744073709551360, 18446744073709551360 };
- _9 = _15 != { 0, 0 };
+ _9 = v.2_7 > { 255, 255 };
and the reason why it happens can be seen in the Applying line, it isn't GIMPLE
but GENERIC even when it happens so late.
#0 optimize_vectors_before_lowering_p () at ../../gcc/generic-match-head.cc:93
#1 0x00000000019d3302 in generic_simplify_NE_EXPR (loc=2147483658,
code=NE_EXPR, type=<vector_type 0x7fffea2ddb28>, _p0=<bit_and_expr
0x7fffea304280>,
_p1=<vector_cst 0x7fffea308cf0>) at generic-match.cc:75147
#2 0x0000000001a46486 in generic_simplify (loc=2147483658, code=NE_EXPR,
type=<vector_type 0x7fffea2ddb28>, _p0=<bit_and_expr 0x7fffea304280>,
_p1=<vector_cst 0x7fffea308cf0>)
at generic-match.cc:102839
#3 0x000000000085e140 in fold_binary_loc (loc=2147483658, code=NE_EXPR,
type=<vector_type 0x7fffea2ddb28>, op0=<bit_and_expr 0x7fffea304280>,
op1=<vector_cst 0x7fffea308cf0>)
at ../../gcc/fold-const.cc:10924
#4 0x0000000000f5c7ea in combine_cond_expr_cond (stmt=<gimple_assign
0x7fffea3020b0>, code=NE_EXPR, type=<vector_type 0x7fffea2ddb28>,
op0=<bit_and_expr 0x7fffea304280>,
op1=<vector_cst 0x7fffea308cf0>, invariant_only=false) at
../../gcc/tree-ssa-forwprop.cc:387
#5 0x0000000000f5ca80 in forward_propagate_into_comparison_1
(stmt=<gimple_assign 0x7fffea3020b0>, code=NE_EXPR, type=<vector_type
0x7fffea2ddb28>,
op0=<ssa_name 0x7fffea3014c8 15>, op1=<vector_cst 0x7fffea308cf0>) at
../../gcc/tree-ssa-forwprop.cc:446
#6 0x0000000000f5cc71 in forward_propagate_into_comparison
(gsi=0x7fffffffd740) at ../../gcc/tree-ssa-forwprop.cc:493
#7 0x0000000000f6bfff in (anonymous namespace)::pass_forwprop::execute
(this=0x37a2170, fun=0x7fffea2fd000) at ../../gcc/tree-ssa-forwprop.cc:3753
next prev parent reply other threads:[~2023-01-03 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 22:52 [Bug middle-end/108237] New: [13 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:281 at -O zsojka at seznam dot cz
2022-12-28 8:52 ` [Bug middle-end/108237] [13 Regression] ICE: in gimple_expand_vec_cond_expr, at gimple-isel.cc:281 at -O since r13-1085-g90467f0ad649d081 marxin at gcc dot gnu.org
2023-01-03 15:57 ` jakub at gcc dot gnu.org
2023-01-03 16:16 ` jakub at gcc dot gnu.org
2023-01-03 16:35 ` jakub at gcc dot gnu.org [this message]
2023-01-03 16:40 ` jakub at gcc dot gnu.org
2023-01-04 9:55 ` cvs-commit at gcc dot gnu.org
2023-01-04 9:56 ` jakub at gcc dot gnu.org
2023-01-09 10:08 ` rguenth at gcc dot gnu.org
2023-02-10 17:45 ` cvs-commit at gcc dot gnu.org
2023-05-02 20:13 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:20 ` cvs-commit 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-108237-4-rbcsMtka6q@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).