public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97984] [10/11 Regression] Worse code for -O3 than -O2 on aarch64 vector multiply-add
Date: Wed, 08 Dec 2021 19:51:12 +0000 [thread overview]
Message-ID: <bug-97984-4-bDeiI9d7M4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97984-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97984
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #4)
> Hm, can't replicate for GCC 10, do you use any -mtune or so?
I can reproduce worse code for GCC 10 at -O3 -mtune=generic:
ldp x2, x3, [x0]
ldr x4, [x1]
ldr q1, [x1]
mul x2, x2, x4
ldr x4, [x1, 8]
fmov d0, x2
ins v0.d[1], x3
mul x1, x3, x4
ins v0.d[1], x1
add v0.2d, v0.2d, v1.2d
str q0, [x0]
But with -O3 -mtune=cortext-a57 the decent code happens.
next prev parent reply other threads:[~2021-12-08 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 11:49 [Bug tree-optimization/97984] New: " ktkachov at gcc dot gnu.org
2020-11-25 12:59 ` [Bug tree-optimization/97984] " rguenth at gcc dot gnu.org
2021-01-14 9:47 ` [Bug target/97984] " rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-11-22 0:49 ` pinskia at gcc dot gnu.org
2021-12-08 14:24 ` marxin at gcc dot gnu.org
2021-12-08 19:51 ` pinskia at gcc dot gnu.org [this message]
2021-12-09 10:05 ` marxin at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug target/97984] [11 " rguenth 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-97984-4-bDeiI9d7M4@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).