public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102066] New: aarch64: Suboptimal addressing modes for SVE LD1W, ST1W Date: Wed, 25 Aug 2021 14:46:53 +0000 [thread overview] Message-ID: <bug-102066-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102066 Bug ID: 102066 Summary: aarch64: Suboptimal addressing modes for SVE LD1W, ST1W Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: ktkachov at gcc dot gnu.org CC: rsandifo at gcc dot gnu.org Target Milestone: --- Target: aarch64 For the code: #include <arm_sve.h> void foo(int n, float *x, float *y) { for (unsigned i=0; i<n; i+=svcntw()) { svfloat32_t val = svld1_f32(svptrue_b8(), &x[i]); svst1_f32(svptrue_b8(), &y[i], val); } } at -O3 -march=armv8.2-a+sve GCC generates: foo: cbz w0, .L1 mov w4, 0 cntw x6 ptrue p0.b, all .L3: ubfiz x3, x4, 2, 32 add w4, w4, w6 add x5, x1, x3 add x3, x2, x3 ld1w z0.s, p0/z, [x5] st1w z0.s, p0, [x3] cmp w4, w0 bcc .L3 .L1: ret but it could be making better use of the addressing modes: foo: // @foo cbz w0, .LBB0_3 mov w8, wzr ptrue p0.b cntw x9 .LBB0_2: // %for.body mov w10, w8 ld1w { z0.s }, p0/z, [x1, x10, lsl #2] add w8, w8, w9 cmp w8, w0 st1w { z0.s }, p0, [x2, x10, lsl #2] b.lo .LBB0_2 .LBB0_3: // %for.cond.cleanup ret I guess the predicates and constraints in @aarch64_pred_mov<mode> in aarch64-sve.md should allow for the scaled address modes
next reply other threads:[~2021-08-25 14:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-25 14:46 ktkachov at gcc dot gnu.org [this message] 2021-08-25 15:01 ` [Bug target/102066] " rsandifo at gcc dot gnu.org 2021-08-25 15:19 ` ktkachov at gcc dot gnu.org 2024-01-26 0:18 ` [Bug tree-optimization/102066] " pinskia at gcc dot gnu.org 2024-01-26 0:19 ` pinskia 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-102066-4@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).