public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yyc1992 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106327] New: side-effect-free _x variance not optimized to unpredicated instruction
Date: Sat, 16 Jul 2022 20:11:38 +0000 [thread overview]
Message-ID: <bug-106327-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106327
Bug ID: 106327
Summary: side-effect-free _x variance not optimized to
unpredicated instruction
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: yyc1992 at gmail dot com
Target Milestone: ---
Related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106326 .
According to the Arm C Language Extension for SVE, when the _x predicate is
used,
> The compiler can then pick whichever form of instruction seems to give the best code. This includes using unpredicated instructions, where available and suitable
Because of this, I'm expecting the following to be optimized to a single add
instruction, as if a `svptrue_b64()` predicate is used.
```
svfloat64_t add(svfloat64_t a, svfloat64_t b)
{
auto und_ok = svcmpge(svptrue_b64(), a, b);
return svadd_x(und_ok, a, b);
}
```
However, gcc compiles this as _m and generates
```
ptrue p0.b, all
fcmge p0.d, p0/z, z0.d, z1.d
fadd z0.d, p0/m, z0.d, z1.d
```
In general, is there any reason not to treat an `add_x` (also other
side-effect-free functions) with an unknown predicate as unpredicated one?
next reply other threads:[~2022-07-16 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 20:11 yyc1992 at gmail dot com [this message]
2022-08-31 11:38 ` [Bug target/106327] " rsandifo 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-106327-4@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).