public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113089] [14 Regression][aarch64] ICE in process_uses_of_deleted_def, at rtl-ssa/changes.cc:252 since r14-6605-gc0911c6b357ba9 Date: Wed, 20 Dec 2023 12:08:08 +0000 [thread overview] Message-ID: <bug-113089-4-lldBrUtPmq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113089-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113089 --- Comment #10 from Alex Coplan <acoplan at gcc dot gnu.org> --- So we have this RTL going into ldp_fusion2: 103: x16:DI=[x15:DI--] REG_INC x15:DI 104: x16:SI=zero_extend([x16:DI]) 105: x16:SI=x11:SI-x16:SI 106: x16:SI=x8:SI*x16:SI+x16:SI 1117: {x26:DI=unspec[[x10:DI-0x30]] 39;x27:DI=unspec[[x10:DI-0x30]] 40;} 1118: x27:SI=zero_extend([x27:DI]) 1119: x27:SI=x11:SI-x27:SI 1048: x20:DI=[x10:DI-0x10] REG_EQUIV [x10:DI-0x10] 1049: x20:SI=zero_extend([x20:DI]) 1050: x20:SI=x11:SI-x20:SI 1367: debug D#22 => x15:DI 1025: x15:DI=[x15:DI] and we try to fuse (103,1025): fusing pair [L=1] (103,1025), base=15, hazards: (104,103), move_range: (103,103) ldp: i103 has wb but subsequent i1025 has non-wb update of base (r15), dropping wb but we fail to update the debug insn 1367 which has a use of the def of x15 in i103 that we're deleting.
next prev parent reply other threads:[~2023-12-20 12:08 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-20 3:12 [Bug target/113089] New: " hliu at amperecomputing dot com 2023-12-20 3:14 ` [Bug target/113089] " pinskia at gcc dot gnu.org 2023-12-20 8:02 ` rguenth at gcc dot gnu.org 2023-12-20 10:21 ` manolis.tsamis at vrull dot eu 2023-12-20 10:22 ` manolis.tsamis at vrull dot eu 2023-12-20 10:30 ` acoplan at gcc dot gnu.org 2023-12-20 10:44 ` acoplan at gcc dot gnu.org 2023-12-20 10:48 ` manolis.tsamis at vrull dot eu 2023-12-20 10:59 ` acoplan at gcc dot gnu.org 2023-12-20 11:03 ` manolis.tsamis at vrull dot eu 2023-12-20 11:05 ` acoplan at gcc dot gnu.org 2023-12-20 12:08 ` acoplan at gcc dot gnu.org [this message] 2024-01-08 12:51 ` jakub at gcc dot gnu.org 2024-01-18 15:08 ` acoplan at gcc dot gnu.org 2024-01-19 9:18 ` acoplan at gcc dot gnu.org 2024-01-23 16:50 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:51 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:51 ` cvs-commit at gcc dot gnu.org 2024-01-23 16:55 ` acoplan 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-113089-4-lldBrUtPmq@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).