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: Wed, 19 Jul 2023 08:55:51 +0000 [thread overview] Message-ID: <bug-110625-4-Mav2ufaDX7@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 --- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- The current issue rate framework was originally written for Neoverse V1 and Neoverse V2. For those cores, it wasn't necessary to make a distinction between scalar integer operations and scalar FP operations: the integer throughput and FP throughput were close enough for the difference not to matter. I think the problem is that the difference between integer throughput and FP throughput does matter for Neoverse N2. E.g. integer additions have a throughput of 4 a cycle whereas FP additions have a throughput of 2 a cycle. Currently the Neoverse N2 model uses a throughput of 4 “general ops” for scalar code. However, when the loop consists entirely of loads, stores and FP operations, the limit should instead be 2.
next prev parent reply other threads:[~2023-07-19 8:55 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 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 [this message] 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-Mav2ufaDX7@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).