From: "H.J. Lu" <hjl.tools@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>,
Lili Cui <lili.cui@intel.com>, Jeff Law <jeffreyalaw@gmail.com>,
Jakub Jelinek <jakub@redhat.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>
Subject: PING^4 [PATCH] x86: Update memcpy/memset inline strategies for -mtune=generic
Date: Fri, 1 Oct 2021 08:24:50 -0700 [thread overview]
Message-ID: <CAMe9rOpkeAkmA1d==Csi2ukBwn1LF6PP_a4uhpWXEvzRsxGxsw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqb--4=E+G6yy-Bsuk1xc=jX1+7FHGn-uvAejsXV9SGoA@mail.gmail.com>
On Mon, Sep 20, 2021 at 10:06 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Mon, Sep 13, 2021 at 6:38 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Tue, Sep 7, 2021 at 8:01 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >
> > > 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
> > >
> >
> > PING. This should fix:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102294
> >
>
> PING.
>
Any comments or objections to this patch?
--
H.J.
prev parent reply other threads:[~2021-10-01 15:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 13:16 [PATCH 0/3] x86: Update memcpy/memset inline strategies H.J. Lu
2021-03-22 13:16 ` [PATCH 1/3] x86: Update memcpy/memset inline strategies for Ice Lake H.J. Lu
2021-03-22 14:10 ` Jan Hubicka
2021-03-22 23:57 ` [PATCH v2 " H.J. Lu
2021-03-29 13:43 ` H.J. Lu
2021-03-31 6:59 ` Richard Biener
2021-03-31 8:05 ` Jan Hubicka
2021-03-31 13:09 ` H.J. Lu
2021-03-31 13:40 ` Jan Hubicka
2021-03-31 13:47 ` Jan Hubicka
2021-03-31 15:41 ` H.J. Lu
2021-03-31 17:43 ` Jan Hubicka
2021-03-31 17:54 ` H.J. Lu
2021-04-01 5:57 ` Hongyu Wang
2021-03-22 13:16 ` [PATCH 2/3] x86: Update memcpy/memset inline strategies for Skylake family CPUs H.J. Lu
2021-04-05 13:45 ` H.J. Lu
2021-04-05 21:14 ` Jan Hubicka
2021-04-05 21:53 ` H.J. Lu
2021-04-06 9:09 ` Hongyu Wang
2021-04-06 9:51 ` Jan Hubicka
2021-04-06 12:34 ` H.J. Lu
2021-03-22 13:16 ` [PATCH 3/3] x86: Update memcpy/memset inline strategies for -mtune=generic H.J. Lu
2021-03-22 13:29 ` Richard Biener
2021-03-22 13:38 ` H.J. Lu
2021-03-23 2:41 ` Hongyu Wang
2021-03-23 8:19 ` Richard Biener
2021-08-22 15:28 ` PING [PATCH] " H.J. Lu
2021-09-08 3:01 ` PING^2 " H.J. Lu
2021-09-13 13:38 ` H.J. Lu
2021-09-20 17:06 ` PING^3 " H.J. Lu
2021-10-01 15:24 ` H.J. Lu [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='CAMe9rOpkeAkmA1d==Csi2ukBwn1LF6PP_a4uhpWXEvzRsxGxsw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=hongyu.wang@intel.com \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=jh@suse.cz \
--cc=lili.cui@intel.com \
--cc=richard.guenther@gmail.com \
--cc=ubizjak@gmail.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).