public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Lili Cui <cuilili@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4124] x86: Enable 256 move by pieces for ALDERLAKE machine.
Date: Thu, 17 Nov 2022 08:27:56 +0000 (GMT)	[thread overview]
Message-ID: <20221117082756.DD3DF3947C34@sourceware.org> (raw)

https://gcc.gnu.org/g:156f523f9582f1e6bcce27ece03f2776960408c8

commit r13-4124-g156f523f9582f1e6bcce27ece03f2776960408c8
Author: Lili Cui <lili.cui@intel.com>
Date:   Thu Nov 17 15:50:46 2022 +0800

    x86: Enable 256 move by pieces for ALDERLAKE machine.
    
    gcc/ChangeLog:
    
            * config/i386/x86-tune.def
            (X86_TUNE_AVX256_MOVE_BY_PIECES): Add alderlake.
            (X86_TUNE_AVX256_STORE_BY_PIECES): Ditto.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/i386/pieces-memset-50.c: New test.

Diff:
---
 gcc/config/i386/x86-tune.def                     |  4 ++--
 gcc/testsuite/gcc.target/i386/pieces-memset-50.c | 12 ++++++++++++
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/gcc/config/i386/x86-tune.def b/gcc/config/i386/x86-tune.def
index 58e29e7806a..cd66f335113 100644
--- a/gcc/config/i386/x86-tune.def
+++ b/gcc/config/i386/x86-tune.def
@@ -536,12 +536,12 @@ DEF_TUNE (X86_TUNE_AVX256_OPTIMAL, "avx256_optimal", m_CORE_AVX512)
 /* X86_TUNE_AVX256_MOVE_BY_PIECES: Optimize move_by_pieces with 256-bit
    AVX instructions.  */
 DEF_TUNE (X86_TUNE_AVX256_MOVE_BY_PIECES, "avx256_move_by_pieces",
-	  m_CORE_AVX512)
+	  m_ALDERLAKE | m_CORE_AVX2)
 
 /* X86_TUNE_AVX256_STORE_BY_PIECES: Optimize store_by_pieces with 256-bit
    AVX instructions.  */
 DEF_TUNE (X86_TUNE_AVX256_STORE_BY_PIECES, "avx256_store_by_pieces",
-	  m_CORE_AVX512)
+	  m_ALDERLAKE | m_CORE_AVX2)
 
 /* X86_TUNE_AVX512_MOVE_BY_PIECES: Optimize move_by_pieces with 512-bit
    AVX instructions.  */
diff --git a/gcc/testsuite/gcc.target/i386/pieces-memset-50.c b/gcc/testsuite/gcc.target/i386/pieces-memset-50.c
new file mode 100644
index 00000000000..c09e7c3649c
--- /dev/null
+++ b/gcc/testsuite/gcc.target/i386/pieces-memset-50.c
@@ -0,0 +1,12 @@
+/* { dg-do compile } */
+/* { dg-options "-O2 -march=alderlake" } */
+
+extern char *dst;
+
+void
+foo (int x)
+{
+  __builtin_memset (dst, x, 64);
+}
+
+/* { dg-final { scan-assembler-times "vmovdqu\[ \\t\]+\[^\n\]*%ymm" 2 } } */

                 reply	other threads:[~2022-11-17  8:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221117082756.DD3DF3947C34@sourceware.org \
    --to=cuilili@gcc.gnu.org \
    --cc=gcc-cvs@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: link
Be 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).