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 target/113690] [13/14 Regression] ICE: in as_a, at machmode.h:381 with -O2 -fno-dce -fno-forward-propagate -fno-split-wide-types -funroll-loops Date: Thu, 01 Feb 2024 01:09:21 +0000 [thread overview] Message-ID: <bug-113690-4-Nh8dEnOyXZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113690-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113690 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|rtl-optimization |target --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (gdb) p debug_rtx(tem) (expr_list:REG_EQUAL (mult:V1TI (reg:V1TI 101 [ _12 ]) (const_int 3 [0x3])) (nil)) That seems wrong ... It was introduced by stv1 pass with: (insn 32 31 33 2 (set (reg:V1TI 132 [ _20 ]) (reg:V1TI 101 [ _12 ])) "t5.c":9:5 2025 {movv1ti_internal} (expr_list:REG_DEAD (reg:V1TI 130 [ BIT_FIELD_REF <v, 128, 128> ]) (expr_list:REG_DEAD (reg:V1TI 129 [ BIT_FIELD_REF <v, 128, 128> ]) (expr_list:REG_UNUSED (reg:CC 17 flags) (expr_list:REG_EQUAL (mult:V1TI (reg:V1TI 101 [ _12 ]) (const_int 3 [0x3])) (nil)))))) Which was before it: (insn 32 31 33 2 (set (reg:TI 132 [ _20 ]) (reg:TI 101 [ _12 ])) "t5.c":9:5 83 {*movti_internal} (expr_list:REG_DEAD (reg:TI 130 [ BIT_FIELD_REF <v, 128, 128> ]) (expr_list:REG_DEAD (reg:TI 129 [ BIT_FIELD_REF <v, 128, 128> ]) (expr_list:REG_UNUSED (reg:CC 17 flags) (expr_list:REG_EQUAL (mult:TI (reg:TI 101 [ _12 ]) (const_int 3 [0x3])) (nil)))))) it should have been replaced with `(const_vect (const_int 3))`. So this is a target specific pass which is causing the issue.
next prev parent reply other threads:[~2024-02-01 1:09 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-31 20:40 [Bug rtl-optimization/113690] New: " zsojka at seznam dot cz 2024-02-01 1:02 ` [Bug rtl-optimization/113690] " pinskia at gcc dot gnu.org 2024-02-01 1:09 ` pinskia at gcc dot gnu.org [this message] 2024-02-01 7:45 ` [Bug target/113690] " rguenth at gcc dot gnu.org 2024-02-01 14:28 ` hjl.tools at gmail dot com 2024-02-01 22:21 ` roger at nextmovesoftware dot com 2024-02-07 14:22 ` cvs-commit at gcc dot gnu.org 2024-02-16 9:07 ` [Bug target/113690] [13 " roger at nextmovesoftware dot com 2024-05-08 12:23 ` rguenth at gcc dot gnu.org 2024-05-21 9:18 ` 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-113690-4-Nh8dEnOyXZ@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).