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/113356] [14 Regression][aarch64] ICE in try_fuse_pair, at config/aarch64/aarch64-ldp-fusion.cc:2203 since r14-6947-g4b67ec7ff5b1aa Date: Fri, 12 Jan 2024 15:07:27 +0000 [thread overview] Message-ID: <bug-113356-4-rk6PUvX6iW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113356-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113356 --- Comment #2 from Alex Coplan <acoplan at gcc dot gnu.org> --- So we have this IR: insn i8 in bb2 [ebb2] at point 18: +---------------------------- | 8: [r104:DI++]=r101:DI | REG_DEAD r101:DI | REG_INC r104:DI +---------------------------- has pre/post-modify operations uses: use of set r101:i7 (DI pseudo) use of set r104:i17 (DI pseudo) appears in a read/write context defines: set r104:i8 (DI pseudo) set by a pre/post-modify appears in a read/write context used by insn i13 in bb2 [ebb2] at point 24 set mem:i8 insn i11 in bb2 [ebb2] at point 20: +------------------------------------------------ | 11: r106:DI=high(const(`_ZTV6Class1'+0x10)) +------------------------------------------------ defines: set r106:i11 (DI pseudo) used by insn i12 in bb2 [ebb2] at point 22 insn i12 in bb2 [ebb2] at point 22: +------------------------------------------------------- | 12: r105:DI=r106:DI+low(const(`_ZTV6Class1'+0x10)) | REG_DEAD r106:DI | REG_EQUAL const(`_ZTV6Class1'+0x10) +------------------------------------------------------- uses: use of set r106:i11 (DI pseudo) defines: set r105:i12 (DI pseudo) used by insn i13 in bb2 [ebb2] at point 24 insn i13 in bb2 [ebb2] at point 24: +---------------------------------------- | 13: [r104:DI]=r105:DI | REG_DEAD r105:DI | REG_DEAD r104:DI | REG_EH_REGION 0xffffffffffffffff +---------------------------------------- uses: use of set r104:i8 (DI pseudo) appears inside an address use of set r105:i12 (DI pseudo) defines: set mem:i13 used by phi node mem:a7 in ebb1 at point 30 and we're trying to form (8,13). i8 has i13 as a hazard due to the writeback dataflow and i13 has i12 as a hazard (due to the initial fix for non-call exceptions introducing a hazard on the previous nondebug insn). I wonder if it would be enough to get i
next prev parent reply other threads:[~2024-01-12 15:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 14:46 [Bug target/113356] New: " mjires at suse dot cz 2024-01-12 14:55 ` [Bug target/113356] " jakub at gcc dot gnu.org 2024-01-12 14:55 ` acoplan at gcc dot gnu.org 2024-01-12 14:55 ` acoplan at gcc dot gnu.org 2024-01-12 15:07 ` acoplan at gcc dot gnu.org [this message] 2024-01-12 15:09 ` acoplan at gcc dot gnu.org 2024-01-15 14:27 ` acoplan at gcc dot gnu.org 2024-01-23 16:50 ` 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-113356-4-rk6PUvX6iW@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).