public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110625] [AArch64] Vect: SLP fails to vectorize a loop as the reduction_latency calculated by new costs is too large Date: Tue, 18 Jul 2023 10:41:11 +0000 [thread overview] Message-ID: <bug-110625-4-4O4QdulQRr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110625-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110625 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsandifo at gcc dot gnu.org --- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- Sorry, didn't see this PR until now. On: > general operations = 15 <-- Too large Are you sure this is too large? The vector code seems to be: ldr q31, [x3], 16 ldr q29, [x4], -16 rev64 v31.8h, v31.8h uxtl v30.4s, v31.4h uxtl2 v31.4s, v31.8h sxtl v27.2d, v30.2s sxtl v28.2d, v31.2s sxtl2 v30.2d, v30.4s sxtl2 v31.2d, v31.4s scvtf v27.2d, v27.2d scvtf v28.2d, v28.2d scvtf v30.2d, v30.2d scvtf v31.2d, v31.2d fmla v26.2d, v27.2d, v29.d[1] fmla v24.2d, v30.2d, v29.d[1] fmla v23.2d, v28.2d, v29.d[0] fmla v25.2d, v31.2d, v29.d[0] Discounting the loads, we do have 15 general operations. On the reduction latency, the: > /* ??? Ideally we'd do COUNT reductions in parallel, but unfortunately > that's not yet the case. */ is referring to the single_defuse_cycle code in vectorizable_reduction. That's always seemed like a misfeature to me, since it serialises a multi-vector reduction through a single accumulator. I guess it's finally time to opt out of that for aarch64. If we did opt out, then removing the “* count” should be correct for all cases.
next prev parent reply other threads:[~2023-07-18 10:41 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 9:15 [Bug target/110625] New: " hliu at amperecomputing dot com 2023-07-11 10:41 ` [Bug target/110625] " rguenth at gcc dot gnu.org 2023-07-12 0:58 ` hliu at amperecomputing dot com 2023-07-14 8:58 ` hliu at amperecomputing dot com 2023-07-18 10:41 ` rsandifo at gcc dot gnu.org [this message] 2023-07-18 12:03 ` rsandifo at gcc dot gnu.org 2023-07-19 2:57 ` hliu at amperecomputing dot com 2023-07-19 8:55 ` rsandifo at gcc dot gnu.org 2023-07-19 9:36 ` hliu at amperecomputing dot com 2023-07-28 16:50 ` rsandifo at gcc dot gnu.org 2023-07-28 16:53 ` rsandifo at gcc dot gnu.org 2023-07-31 2:45 ` hliu at amperecomputing dot com 2023-07-31 12:56 ` cvs-commit at gcc dot gnu.org 2023-08-01 9:09 ` tnfchris at gcc dot gnu.org 2023-08-01 9:19 ` tnfchris at gcc dot gnu.org 2023-08-01 9:45 ` hliu at amperecomputing dot com 2023-08-01 9:49 ` tnfchris at gcc dot gnu.org 2023-08-01 9:50 ` hliu at amperecomputing dot com 2023-08-01 13:49 ` tnfchris at gcc dot gnu.org 2023-08-02 3:49 ` hliu at amperecomputing dot com 2023-08-04 2:34 ` cvs-commit at gcc dot gnu.org 2023-12-08 10:20 ` [Bug target/110625] [14 Regression][AArch64] " tnfchris at gcc dot gnu.org 2023-12-12 16:26 ` tnfchris at gcc dot gnu.org 2023-12-26 14:55 ` tnfchris at gcc dot gnu.org 2023-12-29 15:59 ` cvs-commit at gcc dot gnu.org 2023-12-29 16:16 ` tnfchris at gcc dot gnu.org 2023-12-30 8:34 ` hliu at amperecomputing dot com
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-110625-4-4O4QdulQRr@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).