public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111614] [14 Regression] ICE at -O2: verify_gimple failed since r14-2282-gf703d2fd3f0 Date: Wed, 27 Sep 2023 18:45:43 +0000 [thread overview] Message-ID: <bug-111614-4-3x8YxgtRhB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111614-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111614 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2023-09-27 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Looks like a latent bug in reassoc: ``` vector(2) unsigned int _11; intD.6 _6; intD.6 _8; vect__15.28_19 = VIEW_CONVERT_EXPR<vector(2) intD.6>(_3); _4 = BIT_FIELD_REF <vect__15.28_19, 32, 0>; _35 = BIT_FIELD_REF <vect__15.28_19, 32, 32>; _30 = _35 & _4; _28 = _30 & d_lsm.16_31; ... _62 = VIEW_CONVERT_EXPR<vector(2) unsigned int>(vect_i_7.24_45); _11 = _62 + { 11, 11 }; _6 = BIT_FIELD_REF <_11, 32, 0>; _8 = BIT_FIELD_REF <_11, 32, 32>; _21 = _8 & _6; _34 = _21 & _28; ``` basically BIT_FIELD_REF has a type of `int` but the inner vector type of _11 is `vector unsigned int`. The VCE was removed by the following match pattern: ``` (simplify (BIT_FIELD_REF (view_convert @0) @1 @2) (BIT_FIELD_REF @0 @1 @2)) ``` Which you expect really. Confirmed.
next prev parent reply other threads:[~2023-09-27 18:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-27 13:39 [Bug tree-optimization/111614] New: " shaohua.li at inf dot ethz.ch 2023-09-27 18:36 ` [Bug tree-optimization/111614] " pinskia at gcc dot gnu.org 2023-09-27 18:45 ` pinskia at gcc dot gnu.org [this message] 2023-09-28 7:42 ` rguenth at gcc dot gnu.org 2023-09-28 9:25 ` cvs-commit at gcc dot gnu.org 2023-09-28 9:26 ` [Bug tree-optimization/111614] [11/12/13 " rguenth at gcc dot gnu.org 2023-11-10 14:24 ` cvs-commit at gcc dot gnu.org 2023-11-27 13:09 ` [Bug tree-optimization/111614] [11/12 " cvs-commit at gcc dot gnu.org 2023-12-15 12:18 ` [Bug tree-optimization/111614] [11 " cvs-commit at gcc dot gnu.org 2023-12-15 12:23 ` rguenth at gcc dot gnu.org 2023-12-15 12:23 ` rguenth 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-111614-4-3x8YxgtRhB@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).