From: Noah Goldstein <goldstein.w.n@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>,
"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH v3] x86: Remove __mmask intrinsics in strstr-avx512.c
Date: Tue, 12 Jul 2022 13:12:59 -0700 [thread overview]
Message-ID: <CAFUsyfKjD0j07fKnYUiGhxNDY3M-E_pg+wnmd7a5EGSnN9dLiQ@mail.gmail.com> (raw)
In-Reply-To: <87tu7maz9r.fsf@igel.home>
On Tue, Jul 12, 2022 at 12:48 PM Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> On Jul 12 2022, H.J. Lu via Libc-alpha wrote:
>
> > On Tue, Jul 12, 2022 at 11:48 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> >>
> >> The intrinsics are not available before GCC7 and using standard
> >> operators generates code of equivilent or better quality.
> > generate equivalent
>
> I think "using ... generates" is correct.
Going to check in with just 'equivilent' -> 'equivalent'
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
> "And now for something completely different."
prev parent reply other threads:[~2022-07-12 20:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 22:07 [PATCH v1] x86: Use regular casting instead of _cvtmask64_u64 in strstr-avx512 Noah Goldstein
2022-07-11 22:08 ` Noah Goldstein
2022-07-11 22:17 ` Sunil Pandey
2022-07-11 22:32 ` Noah Goldstein
2022-07-11 22:38 ` [PATCH v2] x86: Remove __mmask intrinsics in strstr-avx512.c Noah Goldstein
2022-07-11 22:52 ` Noah Goldstein
2022-07-11 23:33 ` Sunil Pandey
2022-07-12 2:26 ` H.J. Lu
2022-07-12 2:37 ` Noah Goldstein
2022-07-12 15:56 ` H.J. Lu
2022-07-12 17:11 ` Noah Goldstein
2022-07-12 18:40 ` Noah Goldstein
2022-07-12 18:43 ` H.J. Lu
2022-07-12 18:48 ` Noah Goldstein
2022-07-11 23:32 ` Sunil Pandey
2022-07-12 18:48 ` [PATCH v3] " Noah Goldstein
2022-07-12 19:07 ` H.J. Lu
2022-07-12 19:48 ` Andreas Schwab
2022-07-12 20:12 ` Noah Goldstein [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=CAFUsyfKjD0j07fKnYUiGhxNDY3M-E_pg+wnmd7a5EGSnN9dLiQ@mail.gmail.com \
--to=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).