public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/81904] FMA and addsub instructions
Date: Mon, 31 Jul 2023 05:27:38 +0000 [thread overview]
Message-ID: <bug-81904-4-Hlho6SRJlm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-81904-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81904
--- Comment #5 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> Hmm, I think the issue is we see
>
> f (__m128d x, __m128d y, __m128d z)
> {
> vector(2) double _4;
> vector(2) double _6;
>
> <bb 2> [100.00%]:
> _4 = x_2(D) * y_3(D);
> _6 = __builtin_ia32_addsubpd (_4, z_5(D)); [tail call]
We can fold the builtin into .VEC_ADDSUB, and optimize MUL + VEC_ADDSUB ->
VEC_FMADDSUB in match.pd?
next prev parent reply other threads:[~2023-07-31 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-81904-4@http.gcc.gnu.org/bugzilla/>
2023-07-21 12:31 ` rguenth at gcc dot gnu.org
2023-07-31 5:26 ` crazylht at gmail dot com
2023-07-31 5:27 ` crazylht at gmail dot com [this message]
2023-07-31 7:32 ` rguenth at gcc dot gnu.org
2023-07-31 7:58 ` crazylht at gmail dot com
2023-08-02 6:50 ` cvs-commit at gcc dot gnu.org
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=bug-81904-4-Hlho6SRJlm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).