public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dizhao at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/114674] [aarch64] ldp_fusion fails to merge 2 strs due to imprecise alignment info Date: Wed, 10 Apr 2024 07:43:32 +0000 [thread overview] Message-ID: <bug-114674-4-biFwRWMLRd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114674-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114674 --- Comment #1 from Di Zhao <dizhao at os dot amperecomputing.com> --- Here's a quick fix I tried, that works on the small test case above: diff --git a/gcc/config/aarch64/aarch64-ldp-fusion.cc b/gcc/config/aarch64/aarch64-ldp-fusion.cc index 365dcf48b22..43478ede72b 100644 --- a/gcc/config/aarch64/aarch64-ldp-fusion.cc +++ b/gcc/config/aarch64/aarch64-ldp-fusion.cc @@ -1735,6 +1735,9 @@ ldp_bb_info::fuse_pair (bool load_p, rtx new_mem = adjust_address_nv (effective_base, mode_for_mem, adjust_amt); + // Keep original alignment info for ldp/stp policy. + set_mem_align (new_mem, MEM_ALIGN (change_mem)); + rtx new_set = load_p ? gen_rtx_SET (change_reg, new_mem) : gen_rtx_SET (new_mem, change_reg); Is is OK?
next prev parent reply other threads:[~2024-04-10 7:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-10 7:41 [Bug rtl-optimization/114674] New: " dizhao at os dot amperecomputing.com 2024-04-10 7:43 ` dizhao at os dot amperecomputing.com [this message] 2024-04-10 8:34 ` [Bug rtl-optimization/114674] " acoplan at gcc dot gnu.org 2024-04-10 13:27 ` acoplan at gcc dot gnu.org 2024-04-10 14:00 ` acoplan at gcc dot gnu.org 2024-04-11 6:40 ` dizhao at os dot amperecomputing.com 2024-05-07 13:44 ` cvs-commit at gcc dot gnu.org 2024-05-07 13:46 ` 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-114674-4-biFwRWMLRd@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).