From: Richard Biener <rguenther@suse.de>
To: Hongtao Liu <crazylht@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"Liu, Hongtao" <hongtao.liu@intel.com>
Subject: Re: [PATCH] Add FMADDSUB and FMSUBADD SLP vectorization patterns and optabs
Date: Wed, 7 Jul 2021 09:57:48 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2107070957420.10711@zhemvz.fhfr.qr> (raw)
In-Reply-To: <CAMZc-bwhG6_J3TcHY1yYHY83mXaJfUPu0dK2tGsewPgfeVWeUA@mail.gmail.com>
On Wed, 7 Jul 2021, Hongtao Liu wrote:
> > > > > and I have no easy way to test things there. Handling AVX512
> > > > > should be easy as followup though.
>
> Here's the patch adding avx512f tests for FMADDSUB/FMSUBADD slp patterns.
> Pushed to the trunk.
Thanks!
Richard.
prev parent reply other threads:[~2021-07-07 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 14:09 Richard Biener
2021-07-05 14:25 ` Richard Biener
2021-07-05 14:38 ` Richard Biener
2021-07-06 2:16 ` Hongtao Liu
2021-07-06 7:42 ` Richard Biener
2021-07-06 8:29 ` Hongtao Liu
2021-07-07 7:30 ` Hongtao Liu
2021-07-07 7:57 ` Richard Biener [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=nycvar.YFH.7.76.2107070957420.10711@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.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).