public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Fri, 15 Dec 2023 02:36:35 +0000 [thread overview] Message-ID: <bug-112824-4-WtiOxqLS6x@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 --- Comment #10 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Hongyu Wang <hongyuw@gcc.gnu.org>: https://gcc.gnu.org/g:a52940cfee0908aed0d2a674a451f6d99844444d commit r14-6575-ga52940cfee0908aed0d2a674a451f6d99844444d Author: Hongyu Wang <hongyu.wang@intel.com> Date: Mon Dec 11 09:15:02 2023 +0800 i386: Sync move_max/store_max with prefer-vector-width [PR112824] Currently move_max follows the tuning feature first, but ideally it should sync with prefer-vector-width when it is explicitly set to keep vector move and operation with same vector size. gcc/ChangeLog: PR target/112824 * config/i386/i386-options.cc (ix86_option_override_internal): Sync ix86_move_max/ix86_store_max with prefer_vector_width when it is explicitly set. gcc/testsuite/ChangeLog: PR target/112824 * gcc.target/i386/pieces-memset-45.c: Remove -mprefer-vector-width=256. * g++.target/i386/pr112824-1.C: New test.
prev parent reply other threads:[~2023-12-15 2:36 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 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 [this message]
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-WtiOxqLS6x@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).