public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "liuhongt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112824] Stack spills and vector splitting with vector builtins Date: Mon, 04 Dec 2023 03:42:09 +0000 [thread overview] Message-ID: <bug-112824-4-Tz1aS1v0EC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112824-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112824 liuhongt at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |liuhongt at gcc dot gnu.org --- Comment #4 from liuhongt at gcc dot gnu.org --- there're 2 reasons. 1. X86_TUNE_AVX512_MOVE_BY_PIECES is used for move struct but it's independent of -mprefer-vector-width=512, manully add -mtune-ctrl=-mtune-ctrl=avx512_move_by_pieces can solve most cases. 2. There's still spills for (subreg:DF (reg: V8DF) since ix86_modes_tieable_p return false for DF and V8DF. For 1, I guess when there's explicit -mprefer-vector-width=512, it should rewrite tune X86_TUNE_AVX512_MOVE_BY_PIECES and unset X86_TUNE_AVX256_OPTIMAL/X86_TUNE_AVX128_OPTIMAL For 2, according to doc, it should return false since DF can be allocated to X87 reg, but V8DF only SSE_REGS, so the fix should be using vec_select instead of subreg for that case?
next prev parent reply other threads:[~2023-12-04 3:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-02 11:42 [Bug tree-optimization/112824] New: " elrodc at gmail dot com 2023-12-02 13:20 ` [Bug tree-optimization/112824] " elrodc at gmail dot com 2023-12-03 13:29 ` [Bug middle-end/112824] " elrodc at gmail dot com 2023-12-03 13:58 ` elrodc at gmail dot com 2023-12-04 3:42 ` liuhongt at gcc dot gnu.org [this message] 2023-12-04 10:04 ` rguenth at gcc dot gnu.org 2023-12-04 16:43 ` elrodc at gmail dot com 2023-12-05 3:44 ` liuhongt at gcc dot gnu.org 2023-12-05 5:06 ` elrodc at gmail dot com 2023-12-07 7:21 ` wwwhhhyyy333 at gmail dot com 2023-12-15 2:36 ` 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-112824-4-Tz1aS1v0EC@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).