public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schnetter at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99912] Unnecessary / inefficient spilling of AVX2 ymm registers Date: Tue, 27 Apr 2021 16:03:21 +0000 [thread overview] Message-ID: <bug-99912-4-Ry0o77jyrT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99912 --- Comment #11 from Erik Schnetter <schnetter at gmail dot com> --- The number of active local variables is likely much larger than the number of registers, and I expect there to be a lot of spilling. I hope that the compiler is clever about changing the order in which expressions are evaluated to reduce spilling as much as possible. Because the loop is so large, I split it into two, each calculating about half of the output variables. The code here looks at one of the loops. To simplify the code, each loop still loads all variables (via masked loads), but may not use all of them. The unused masked loads do not surprise me per se, but I expect the compiler to remove them.
next prev parent reply other threads:[~2021-04-27 16:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-05 1:53 [Bug target/99912] New: " schnetter at gmail dot com 2021-04-05 1:54 ` [Bug target/99912] " schnetter at gmail dot com 2021-04-05 2:03 ` schnetter at gmail dot com 2021-04-06 8:25 ` rguenth at gcc dot gnu.org 2021-04-06 14:42 ` schnetter at gmail dot com 2021-04-06 16:33 ` schnetter at gmail dot com 2021-04-07 9:36 ` rguenth at gcc dot gnu.org 2021-04-07 16:48 ` rguenth at gcc dot gnu.org 2021-04-27 13:17 ` cvs-commit at gcc dot gnu.org 2021-04-27 13:17 ` cvs-commit at gcc dot gnu.org 2021-04-27 14:02 ` rguenth at gcc dot gnu.org 2021-04-27 16:03 ` schnetter at gmail dot com [this message] 2021-04-29 6:32 ` cvs-commit 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-99912-4-Ry0o77jyrT@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).