From: Noah Goldstein <goldstein.w.n@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@systemhalted.org>
Subject: Re: [PATCH v1 1/3] Bench: Expand bench-memchr.c
Date: Mon, 3 May 2021 15:51:49 -0400 [thread overview]
Message-ID: <CAFUsyfLMX5drerC2-c+dBmpjyq8TGxRyM_env2u-9SXDsQKoNg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOrC3xqXNvsdo+Tcq6d5n_SjmCPa2pn9Ce2tFPK_HUwpsw@mail.gmail.com>
On Mon, May 3, 2021 at 1:18 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Mon, May 3, 2021 at 1:45 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> >
> > No bug. This commit adds some additional cases for bench-memchr.c
> > including testing medium sizes and testing short length with both an
> > inbound match and out of bound match.
> >
> > Signed-off-by: Noah Goldstein <goldstein.w.n@gmail.com>
> > ---
> > benchtests/bench-memchr.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/benchtests/bench-memchr.c b/benchtests/bench-memchr.c
> > index f5ced9d80d..5573f93312 100644
> > --- a/benchtests/bench-memchr.c
> > +++ b/benchtests/bench-memchr.c
> > @@ -135,12 +135,25 @@ test_main (void)
> > do_test (i, i, 256, 0);
> > #endif
> > }
> > + for (i = 1; i < 8; ++i)
> > + {
> > + do_test (i, i << 5, 192, 23);
> > + do_test (i, i << 5, 192, 0);
> > + do_test (i, i << 5, 256, 23);
> > + do_test (i, i << 5, 256, 0);
> > + do_test (i, i << 5, 512, 23);
> > + do_test (i, i << 5, 512, 0);
> > + }
> > for (i = 1; i < 32; ++i)
> > {
> > do_test (0, i, i + 1, 23);
> > do_test (0, i, i + 1, 0);
> > do_test (i, i, i + 1, 23);
> > do_test (i, i, i + 1, 0);
> > + do_test (0, i, i - 1, 23);
> > + do_test (0, i, i - 1, 0);
> > + do_test (i, i, i - 1, 23);
> > + do_test (i, i, i - 1, 0);
> > #ifdef USE_AS_MEMRCHR
> > /* Also test the position close to the beginning for memrchr. */
> > do_test (0, 1, i + 1, 23);
> > --
> > 2.29.2
> >
>
> LGTM. I will check it in for you.
Thanks!
>
> BTW, can you apply an account on sourceware.org:
>
> https://sourceware.org/
>
> so that you can push your commits directly? You can put me down
> as your sponsor.
Done. Are there any wikis / manuals on how to properly use write access?
All I'm finding are resources on how to obtain it.
>
> Thanks.
>
> --
> H.J.
next prev parent reply other threads:[~2021-05-03 19:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 8:44 Noah Goldstein
2021-05-03 8:44 ` [PATCH v1 2/3] x86: Optimize memchr-avx2.S Noah Goldstein
2021-05-03 18:50 ` H.J. Lu
2021-05-03 20:06 ` Noah Goldstein
2021-05-03 20:06 ` [PATCH v2 " Noah Goldstein
2021-05-03 20:06 ` [PATCH v2 3/3] x86: Optimize memchr-evex.S Noah Goldstein
2021-05-03 22:26 ` H.J. Lu
2021-05-03 22:58 ` Noah Goldstein
2021-05-03 22:25 ` [PATCH v2 2/3] x86: Optimize memchr-avx2.S H.J. Lu
2021-05-03 22:58 ` Noah Goldstein
2021-05-03 22:58 ` [PATCH v3 " Noah Goldstein
2021-05-03 22:58 ` [PATCH v3 3/3] x86: Optimize memchr-evex.S Noah Goldstein
2021-05-03 22:59 ` Noah Goldstein
2021-05-03 22:59 ` [PATCH v3 2/3] x86: Optimize memchr-avx2.S Noah Goldstein
2021-05-03 8:44 ` [PATCH v1 3/3] x86: Optimize memchr-evex.S Noah Goldstein
2021-05-03 18:58 ` H.J. Lu
2021-05-03 20:06 ` Noah Goldstein
2021-05-03 17:17 ` [PATCH v1 1/3] Bench: Expand bench-memchr.c H.J. Lu
2021-05-03 19:51 ` Noah Goldstein [this message]
2021-05-03 20:59 ` 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=CAFUsyfLMX5drerC2-c+dBmpjyq8TGxRyM_env2u-9SXDsQKoNg@mail.gmail.com \
--to=goldstein.w.n@gmail.com \
--cc=carlos@systemhalted.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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).