From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <hjl.tools@gmail.com>
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com
 [IPv6:2607:f8b0:4864:20::630])
 by sourceware.org (Postfix) with ESMTPS id F199D385E82E
 for <gcc-patches@gcc.gnu.org>; Wed,  8 Sep 2021 03:02:21 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org F199D385E82E
Received: by mail-pl1-x630.google.com with SMTP id u1so403962plq.5
 for <gcc-patches@gcc.gnu.org>; Tue, 07 Sep 2021 20:02:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=lYPPqT892L/GQaI/UYMYAUoFqw/FmxCDdsk00QVx+Ss=;
 b=GTiEcz5YMRwbnna+r0JIRx7OZjab1IzLWbNDU5ZV1SJxgYLey6Dny/sEsaYcDAaSo3
 8vwBqIIEv5KBeqKXeLvjK+k7w30fA5IP1100d45kBw6g3CcigBRGg4hv1f51f1qe97Jz
 caUL3egSzP0aBXtJ3QADY38L5uyzHQgCirS16E35YalVNhtNyTGwjgcJup6N8e7loF03
 wgYbCUwnZPiMWjU5ufSc+bVB+/8mXIiAyjYiJvQgIYMj79M1dgp7bC5hLMeLBR3txBbw
 5Y10wKrWhVmIsssfJc2mX81b9o9uqwVm43duVvjJHAGrOsfQBhsWVkAPStX3R1FYFyzy
 sMJw==
X-Gm-Message-State: AOAM532vLO0AuBIZUMWDInRCPZPvpp2MViOXwpLf+c0fYF/4xABskkE9
 oUXM+Kg4dH5cfVuoYws+QXkKA7ai6J47z5tYdqc=
X-Google-Smtp-Source: ABdhPJxA61Xf0YjFYqoMFv20TUUZUxlvJiHW1/nVZQZKmzpb3ZKhQr5ebwMLH+qFfw9o3Y+RG2Z1D0KSEXD4zeTxZ1M=
X-Received: by 2002:a17:90b:3812:: with SMTP id
 mq18mr1662075pjb.143.1631070141024; 
 Tue, 07 Sep 2021 20:02:21 -0700 (PDT)
MIME-Version: 1.0
References: <20210322131636.58461-1-hjl.tools@gmail.com>
 <20210322131636.58461-4-hjl.tools@gmail.com>
 <CAFiYyc2GiDP4bU9vVwmiK-zXarBuELd5dRkjtK18a1tZNYTvqw@mail.gmail.com>
 <CAMe9rOp0ptAZd4X9RyqXoDVged=9UfnmyOFV_+c=JHbj0Dpa=w@mail.gmail.com>
 <CA+OydWnRAt2rfN-9iGXdE=LLky2yovWLAP=iJ6QxECKu5xb1Sw@mail.gmail.com>
 <CAFiYyc1Se2k94sgUAamE1QtX5RfpO7uoOojCfS1hv1cz_Y6jMw@mail.gmail.com>
 <YSJtKKbBGoDI4hOd@gmail.com>
In-Reply-To: <YSJtKKbBGoDI4hOd@gmail.com>
From: "H.J. Lu" <hjl.tools@gmail.com>
Date: Tue, 7 Sep 2021 20:01:45 -0700
Message-ID: <CAMe9rOqW-aaboppZKmU=5W0RFBOrei_02eqo2spNGeYjRyLyeg@mail.gmail.com>
Subject: PING^2 [PATCH] x86: Update memcpy/memset inline strategies for
 -mtune=generic
To: Richard Biener <richard.guenther@gmail.com>, Lili Cui <lili.cui@intel.com>
Cc: Uros Bizjak <ubizjak@gmail.com>, Jan Hubicka <jh@suse.cz>,
 Hongtao Liu <hongtao.liu@intel.com>, 
 GCC Patches <gcc-patches@gcc.gnu.org>, Hongyu Wang <hongyu.wang@intel.com>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-3025.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT,
 RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gcc-patches@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>,
 <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>,
 <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2021 03:02:26 -0000

On Sun, Aug 22, 2021 at 8:28 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Tue, Mar 23, 2021 at 09:19:38AM +0100, Richard Biener wrote:
> > On Tue, Mar 23, 2021 at 3:41 AM Hongyu Wang <wwwhhhyyy333@gmail.com> wrote:
> > >
> > > > Hongyue, please collect code size differences on SPEC CPU 2017 and
> > > > eembc.
> > >
> > > Here is code size difference for this patch
> >
> > Thanks, nothing too bad although slightly larger impacts than envisioned.
> >
>
> PING.
>
> OK for master branch?
>
> Thanks.
>
> H.J.
>  ---
> Simplify memcpy and memset inline strategies to avoid branches for
> -mtune=generic:
>
> 1. With MOVE_RATIO and CLEAR_RATIO == 17, GCC will use integer/vector
>    load and store for up to 16 * 16 (256) bytes when the data size is
>    fixed and known.
> 2. Inline only if data size is known to be <= 256.
>    a. Use "rep movsb/stosb" with simple code sequence if the data size
>       is a constant.
>    b. Use loop if data size is not a constant.
> 3. Use memcpy/memset libray function if data size is unknown or > 256.
>

PING:

https://gcc.gnu.org/pipermail/gcc-patches/2021-August/577889.html

-- 
H.J.