public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@systemhalted.org>
Subject: Re: [PATCH v1] x86: Fallback {str|wcs}cmp RTM in the ncmp overflow case [BZ #28896]
Date: Tue, 15 Feb 2022 10:49:37 -0800	[thread overview]
Message-ID: <CAMe9rOrHg57ZanH-zhoyLqvq2rt9sSR3x8ck0cxSDYkL8ecVTQ@mail.gmail.com> (raw)
In-Reply-To: <CAFUsyfKJNtTsE5uTuV1w36EE-pEc5MX+J+HgQQvLS+Ab8Dw_8A@mail.gmail.com>

On Tue, Feb 15, 2022 at 9:06 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
>
> On Tue, Feb 15, 2022 at 11:00 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Tue, Feb 15, 2022 at 8:51 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > >
> > > On Tue, Feb 15, 2022 at 10:30 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> > > >
> > > > On Tue, Feb 15, 2022 at 8:28 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > > > >
> > > > > In the overflow fallback strncmp-avx2-rtm and wcsncmp-avx2-rtm would
> > > > > call strcmp-avx2 and wcsncmp-avx2 respectively. This would have
> > > > > not checks around vzeroupper and would trigger spurious
> > > > > aborts. This commit fixes that.
> > > >
> > > > Include a testcase?
> > > Added test case in V2. Don't have the hardware to check it though,
> > > can you?
> >
> > Yes, I can.  Please V2 on a branch in gitlab.
>
> https://gitlab.com/x86-glibc/glibc/-/commits/users/goldsteinn/strncmp-rtm-test

I updated your branch with some fixes in the testcase and the commit log.
I tested it on an AVX2 machine with RTM.  The testcase fails without your
fix.

Please submit the v2 patch.

Thanks.

-- 
H.J.

  reply	other threads:[~2022-02-15 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 16:27 Noah Goldstein
2022-02-15 16:29 ` H.J. Lu
2022-02-15 16:51   ` Noah Goldstein
2022-02-15 16:59     ` H.J. Lu
2022-02-15 17:06       ` Noah Goldstein
2022-02-15 18:49         ` H.J. Lu [this message]
2022-02-16  8:10           ` Noah Goldstein
2022-02-15 16:49 ` [PATCH v2] " Noah Goldstein
2022-02-16  8:09 ` [PATCH v3] " Noah Goldstein
2022-02-16 13:17   ` H.J. Lu
2022-02-16 14:08     ` Carlos O'Donell
2022-02-16 14:26       ` H.J. Lu
2022-02-17 19:15         ` Noah Goldstein
2022-02-17 19:12 ` [PATCH v4] " Noah Goldstein
2022-02-17 19:15 ` [PATCH v5] " Noah Goldstein
2022-02-17 19:20   ` H.J. Lu
2022-05-25 19:51     ` Sunil Pandey
2022-05-25 19:56       ` 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=CAMe9rOrHg57ZanH-zhoyLqvq2rt9sSR3x8ck0cxSDYkL8ecVTQ@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=goldstein.w.n@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).