public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH v2] x86: Update STORE_MAX_PIECES
Date: Wed, 4 Aug 2021 06:33:54 -0700	[thread overview]
Message-ID: <CAMe9rOoh6gqyQaoD8TuQKuVEbBfP4wz3KyoFemvoHRCF=dME+A@mail.gmail.com> (raw)
In-Reply-To: <20210803135646.2545430-1-hjl.tools@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]

On Tue, Aug 3, 2021 at 6:56 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> 1. Update x86 STORE_MAX_PIECES to use OImode and XImode only if inter-unit
> move is enabled since x86 uses vec_duplicate, which is enabled only when
> inter-unit move is enabled, to implement store_by_pieces.
> 2. Update op_by_pieces_d::op_by_pieces_d to set m_max_size to
> STORE_MAX_PIECES for store_by_pieces and to COMPARE_MAX_PIECES for
> compare_by_pieces.
>
> gcc/
>
>         PR target/101742
>         * expr.c (op_by_pieces_d::op_by_pieces_d): Set m_max_size to
>         STORE_MAX_PIECES for store_by_pieces and to COMPARE_MAX_PIECES
>         for compare_by_pieces.
>         * config/i386/i386.h (STORE_MAX_PIECES): Use OImode and XImode
>         only if TARGET_INTER_UNIT_MOVES_TO_VEC is true.
>
> gcc/testsuite/
>
>         PR target/101742
>         * gcc.target/i386/pr101742a.c: New test.
>         * gcc.target/i386/pr101742b.c: Likewise.
> ---
>  gcc/config/i386/i386.h                    | 20 +++++++++++---------
>  gcc/expr.c                                |  6 +++++-
>  gcc/testsuite/gcc.target/i386/pr101742a.c | 16 ++++++++++++++++
>  gcc/testsuite/gcc.target/i386/pr101742b.c |  4 ++++
>  4 files changed, 36 insertions(+), 10 deletions(-)
>  create mode 100644 gcc/testsuite/gcc.target/i386/pr101742a.c
>  create mode 100644 gcc/testsuite/gcc.target/i386/pr101742b.c
>
> diff --git a/gcc/config/i386/i386.h b/gcc/config/i386/i386.h
> index bed9cd9da18..9b416abd5f4 100644
> --- a/gcc/config/i386/i386.h
> +++ b/gcc/config/i386/i386.h
> @@ -1783,15 +1783,17 @@ typedef struct ix86_args {
>  /* STORE_MAX_PIECES is the number of bytes at a time that we can
>     store efficiently.  */
>  #define STORE_MAX_PIECES \
> -  ((TARGET_AVX512F && !TARGET_PREFER_AVX256) \
> -   ? 64 \
> -   : ((TARGET_AVX \
> -       && !TARGET_PREFER_AVX128 \
> -       && !TARGET_AVX256_SPLIT_UNALIGNED_STORE) \
> -      ? 32 \
> -      : ((TARGET_SSE2 \
> -         && TARGET_SSE_UNALIGNED_STORE_OPTIMAL) \
> -        ? 16 : UNITS_PER_WORD)))
> +  (TARGET_INTER_UNIT_MOVES_TO_VEC \
> +   ? ((TARGET_AVX512F && !TARGET_PREFER_AVX256) \
> +      ? 64 \
> +      : ((TARGET_AVX \
> +         && !TARGET_PREFER_AVX128 \
> +         && !TARGET_AVX256_SPLIT_UNALIGNED_STORE) \
> +         ? 32 \
> +         : ((TARGET_SSE2 \
> +             && TARGET_SSE_UNALIGNED_STORE_OPTIMAL) \
> +             ? 16 : UNITS_PER_WORD))) \
> +   : UNITS_PER_WORD)
>
>  /* If a memory-to-memory move would take MOVE_RATIO or more simple
>     move-instruction pairs, we will do a cpymem or libcall instead.

expr.c has been fixed.   Here is the v2 patch for x86 backend.
OK for master?

Thanks.

-- 
H.J.

[-- Attachment #2: v2-0001-x86-Update-STORE_MAX_PIECES.patch --]
[-- Type: application/x-patch, Size: 2930 bytes --]

  parent reply	other threads:[~2021-08-04 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 13:56 [PATCH] by_pieces: Properly set m_max_size in op_by_pieces H.J. Lu
2021-08-03 21:22 ` H.J. Lu
2021-08-04  7:27   ` Richard Sandiford
2021-08-04 12:52     ` [PATCH v2] by_pieces: Pass MAX_PIECES to op_by_pieces_d H.J. Lu
2021-08-04 13:33 ` H.J. Lu [this message]
2021-08-04 18:46   ` [PATCH v2] x86: Update STORE_MAX_PIECES Uros Bizjak
2021-08-04 20:01     ` [PATCH v3] " H.J. Lu

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='CAMe9rOoh6gqyQaoD8TuQKuVEbBfP4wz3KyoFemvoHRCF=dME+A@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@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).