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/113613] [14 Regression] Missing ldp/stp optimization since r14-6290-g9f0f7d802482a8 Date: Fri, 26 Jan 2024 08:58:55 +0000 [thread overview] Message-ID: <bug-113613-4-rjHoyEX6ki@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113613-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113613 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsandifo at gcc dot gnu.org Summary|[14 Regression] Missing |[14 Regression] Missing |ldp/stp optimization |ldp/stp optimization since |sometimes |r14-6290-g9f0f7d802482a8 --- Comment #4 from Alex Coplan <acoplan at gcc dot gnu.org> --- Interestingly we started to miss this with the introduction of aarch64 early RA i.e. r14-6290-g9f0f7d802482a8958d6cdc72f1fe0c8549db2182. My ldp/stp pattern rewrite was: r14-6604-gd7ee988c491cde43d04fe25f2b3dbad9d85ded45 so we started to miss this before any of my ldp/stp patches. Looking at what happens with the ldp/stp pass, I can see that in sched1 we've already allocated hard regs to the vector load destinations: 3: NOTE_INSN_BASIC_BLOCK 2 2: NOTE_INSN_FUNCTION_BEG 13: NOTE_INSN_DELETED 5: debug begin stmt marker 6: r107:DI=high(`*.LANCHOR0') 7: r106:DI=r107:DI+low(`*.LANCHOR0') REG_EQUAL `*.LANCHOR0' 14: v31:V2SF=[r107:DI+low(`*.LANCHOR0')] 15: v30:V2SF=[r106:DI+0x20] 16: v30:V2SF=v31:V2SF+v30:V2SF REG_DEAD v31:V2SF 27: v31:V2SF=[r106:DI+0x8] 17: [r107:DI+low(`*.LANCHOR0')]=v30:V2SF REG_DEAD r107:DI REG_DEAD v30:V2SF 18: debug begin stmt marker 28: v30:V2SF=[r106:DI+0x28] 29: v30:V2SF=v31:V2SF+v30:V2SF REG_DEAD v31:V2SF 30: [r106:DI+0x8]=v30:V2SF REG_DEAD r106:DI REG_DEAD v30:V2SF 33: NOTE_INSN_DELETED and then there's nothing that the early ldp/stp pass can do because the would-be load pair candidates already use the same (hard) transfer register due to early RA: merge_pairs [L=1], cand vecs (14) x (27) analyzing pair (load=1): (14,27) punting on ldp due to reg conflcits (14,27) merge_pairs [L=1], cand vecs (15) x (28) analyzing pair (load=1): (15,28) punting on ldp due to reg conflcits (15,28) merge_pairs [L=0], cand vecs (17) x (30) analyzing pair (load=0): (17,30) pair (17,30): rejecting base 106 due to dataflow hazards (28,29) can't form pair (17,30) due to dataflow hazards starting the processing of deferred insns ending the processing of deferred insns CCing Richard S for an opinion.
next prev parent reply other threads:[~2024-01-26 8:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-26 6:04 [Bug target/113613] New: [14 Regression] Missing ldp/stp optimization sometimes pinskia at gcc dot gnu.org 2024-01-26 6:05 ` [Bug target/113613] " pinskia at gcc dot gnu.org 2024-01-26 6:39 ` pinskia at gcc dot gnu.org 2024-01-26 8:34 ` acoplan at gcc dot gnu.org 2024-01-26 8:58 ` acoplan at gcc dot gnu.org [this message] 2024-01-26 9:00 ` [Bug target/113613] [14 Regression] Missing ldp/stp optimization since r14-6290-g9f0f7d802482a8 acoplan at gcc dot gnu.org 2024-01-26 9:05 ` acoplan at gcc dot gnu.org 2024-01-26 9:33 ` acoplan at gcc dot gnu.org 2024-01-26 10:20 ` rsandifo at gcc dot gnu.org 2024-02-23 14:13 ` cvs-commit at gcc dot gnu.org 2024-02-23 14:16 ` rsandifo 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-113613-4-rjHoyEX6ki@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).