public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107920] [13 Regression] ICE in execute_todo, at passes.cc:2140 Date: Wed, 30 Nov 2022 16:56:13 +0000 [thread overview] Message-ID: <bug-107920-4-nCjcNco5OC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107920-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107920 --- Comment #11 from prathamesh3492 at gcc dot gnu.org --- Created attachment 53992 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53992&action=edit untested fix Thanks for the suggestions. The attached patch uses gsi_replace_with_seq_vops for preserving VUSE, which prevents the issue and results in following dump for fre: <bb 2> : # VUSE <.MEM_2(D)> _5 = MEM <vector(16) signed char> [(signed char * {ref-all})x_3(D)]; _4 = VEC_PERM_EXPR <_5, _5, { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, ... }>; # VUSE <.MEM_2(D)> return _4; and following code-gen: test_s8: ldr q0, [x0] dup z0.q, z0.q[0] ret I am not sure tho if using update_ssa in the patch is ideal. If not, could you please suggest a better alternative ? Thanks, Prathamesh
next prev parent reply other threads:[~2022-11-30 16:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-29 16:53 [Bug tree-optimization/107920] New: " asolokha at gmx dot com 2022-11-29 18:42 ` [Bug tree-optimization/107920] " pinskia at gcc dot gnu.org 2022-11-29 18:46 ` pinskia at gcc dot gnu.org 2022-11-29 18:50 ` pinskia at gcc dot gnu.org 2022-11-29 18:51 ` pinskia at gcc dot gnu.org 2022-11-29 19:18 ` pinskia at gcc dot gnu.org 2022-11-29 19:54 ` pinskia at gcc dot gnu.org 2022-11-29 19:59 ` [Bug target/107920] " pinskia at gcc dot gnu.org 2022-11-29 20:12 ` pinskia at gcc dot gnu.org 2022-11-29 20:36 ` pinskia at gcc dot gnu.org 2022-11-30 11:48 ` rguenth at gcc dot gnu.org 2022-11-30 11:51 ` rguenth at gcc dot gnu.org 2022-11-30 16:56 ` prathamesh3492 at gcc dot gnu.org [this message] 2022-12-01 12:22 ` jakub at gcc dot gnu.org 2022-12-01 18:06 ` prathamesh3492 at gcc dot gnu.org 2022-12-02 9:13 ` prathamesh3492 at gcc dot gnu.org 2022-12-07 8:06 ` cvs-commit at gcc dot gnu.org 2022-12-08 15:55 ` 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-107920-4-nCjcNco5OC@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).