From: Hongtao Liu <crazylht@gmail.com>
To: "Cui,Lili" <lili.cui@intel.com>
Cc: gcc-patches@gcc.gnu.org, hongtao.liu@intel.com
Subject: Re: [PATCH] x86: Enable 256 move by pieces for ALDERLAKE and AVX2.
Date: Thu, 17 Nov 2022 10:30:51 +0800 [thread overview]
Message-ID: <CAMZc-byBnmy1QTK7aFc_=PuSGC7K33Jjuoef7tiVU1Qpn=UZjw@mail.gmail.com> (raw)
In-Reply-To: <20221111090838.7194-1-lili.cui@intel.com>
On Fri, Nov 11, 2022 at 5:09 PM Cui,Lili via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> From: Lili Cui <lili.cui@intel.com>
>
> Hi Hontao,
>
> This patch is to enable 256 move by pieces for ALDERLAKE and AVX2.
> Bootstrap is ok, and no regressions for i386/x86-64 testsuite.
>
> OK for master?
Ok.
>
>
> gcc/Changelog:
>
> * config/i386/x86-tune.def
> (X86_TUNE_AVX256_MOVE_BY_PIECES): Add alderlake and avx2.
> (X86_TUNE_AVX256_STORE_BY_PIECES): Ditto.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/i386/pieces-memset-50.c: New test.
> ---
> gcc/config/i386/x86-tune.def | 4 ++--
> gcc/testsuite/gcc.target/i386/pieces-memset-50.c | 12 ++++++++++++
> 2 files changed, 14 insertions(+), 2 deletions(-)
> create mode 100644 gcc/testsuite/gcc.target/i386/pieces-memset-50.c
>
> 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 } } */
> --
> 2.17.1
>
> Thanks,
> Lili.
--
BR,
Hongtao
prev parent reply other threads:[~2022-11-17 2:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 9:08 Cui,Lili
2022-11-17 2:30 ` Hongtao Liu [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='CAMZc-byBnmy1QTK7aFc_=PuSGC7K33Jjuoef7tiVU1Qpn=UZjw@mail.gmail.com' \
--to=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=lili.cui@intel.com \
/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).