public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109072] New: [12/13 Regression] SLP costs for vec duplicate too high since g:4963079769c99c4073adfd799885410ad484cbbe Date: Wed, 08 Mar 2023 22:32:22 +0000 [thread overview] Message-ID: <bug-109072-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109072 Bug ID: 109072 Summary: [12/13 Regression] SLP costs for vec duplicate too high since g:4963079769c99c4073adfd799885410ad484cbbe Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: tnfchris at gcc dot gnu.org CC: rsandifo at gcc dot gnu.org Target Milestone: --- Target: aarch64* The following example --- #include <arm_neon.h> float32x4_t f (float32x4_t v, float res) { float data[4]; data[0] = res; data[1] = res; data[2] = res; data[3] = res; return vld1q_f32 (&data[0]); } --- compiled with -Ofast fails to SLP starting with GCC 12. This used to generate: f: dup v0.4s, v1.s[0] ret and now generates: f: fmov w5, s1 fmov w1, s1 fmov w4, s1 fmov w0, s1 mov x2, 0 mov x3, 0 bfi x2, x5, 0, 32 bfi x3, x1, 0, 32 bfi x2, x4, 32, 32 bfi x3, x0, 32, 32 fmov d0, x2 ins v0.d[1], x3 ret The SLP costs went from: Vector cost: 2 Scalar cost: 4 to: Vector cost: 12 Scalar cost: 4 it looks like it's no longer costing it as a duplicate but instead 4 vec inserts. bisected to: commit g:4963079769c99c4073adfd799885410ad484cbbe Author: Richard Sandiford <richard.sandiford@arm.com> Date: Tue Feb 15 18:09:33 2022 +0000 vect+aarch64: Fix ldp_stp_* regressions ldp_stp_1.c, ldp_stp_4.c and ldp_stp_5.c have been failing since vectorisation was enabled at -O2. In all three cases SLP is generating vector code when scalar code would be better. ....
next reply other threads:[~2023-03-08 22:32 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-08 22:32 tnfchris at gcc dot gnu.org [this message] 2023-03-09 10:19 ` [Bug target/109072] " rguenth at gcc dot gnu.org 2023-03-09 14:13 ` rsandifo at gcc dot gnu.org 2023-03-09 14:30 ` tnfchris at gcc dot gnu.org 2023-03-09 14:46 ` rsandifo at gcc dot gnu.org 2023-03-09 15:04 ` tnfchris at gcc dot gnu.org 2023-03-09 16:22 ` rsandifo at gcc dot gnu.org 2023-03-09 17:35 ` rsandifo at gcc dot gnu.org 2023-03-10 7:40 ` rguenth at gcc dot gnu.org 2023-03-10 8:50 ` rsandifo at gcc dot gnu.org 2023-03-15 14:29 ` rguenth at gcc dot gnu.org 2023-03-28 11:35 ` cvs-commit at gcc dot gnu.org 2023-03-28 12:59 ` [Bug target/109072] [12 " rsandifo at gcc dot gnu.org 2023-04-03 8:58 ` cvs-commit at gcc dot gnu.org 2023-04-03 9:03 ` 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-109072-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).