public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jens.seifert at de dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106770] New: PPCLE: Unnecessary xxpermdi before mfvsrd
Date: Mon, 29 Aug 2022 07:52:26 +0000 [thread overview]
Message-ID: <bug-106770-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106770
Bug ID: 106770
Summary: PPCLE: Unnecessary xxpermdi before mfvsrd
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jens.seifert at de dot ibm.com
Target Milestone: ---
#include <altivec.h>
int cmp2(double a, double b)
{
vector double va = vec_promote(a, 1);
vector double vb = vec_promote(b, 1);
vector long long vlt = (vector long long)vec_cmplt(va, vb);
vector long long vgt = (vector long long)vec_cmplt(vb, va);
vector signed long long vr = vec_sub(vlt, vgt);
return vec_extract(vr, 1);
}
Generates:
_Z4cmp2dd:
.LFB1:
.cfi_startproc
xxpermdi 1,1,1,0
xxpermdi 2,2,2,0
xvcmpgtdp 33,2,1
xvcmpgtdp 32,1,2
vsubudm 0,1,0
xxpermdi 0,32,32,3
mfvsrd 3,0
extsw 3,3
blr
The unnecessary xxpermdi for vec_promote are already reported in another
bugzilla case.
mfvsrd can access all 64 vector registers directly and xxpermdi is not
required.
mfvsrd 3,32 expected instead xxpermdi 0,32,32,3 + mfvsrd 3,0
next reply other threads:[~2022-08-29 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 7:52 jens.seifert at de dot ibm.com [this message]
2022-08-29 8:16 ` [Bug target/106770] " jens.seifert at de dot ibm.com
2022-08-29 9:57 ` jens.seifert at de dot ibm.com
2023-02-27 16:26 ` segher at gcc dot gnu.org
2023-02-27 17:57 ` jens.seifert at de dot ibm.com
2023-02-27 23:06 ` segher at gcc dot gnu.org
2023-02-28 7:23 ` jens.seifert at de dot ibm.com
2023-02-28 16:57 ` segher at gcc dot gnu.org
2023-03-02 6:11 ` [Bug target/106770] powerpc64le: " jskumari at gcc dot gnu.org
2023-03-02 7:36 ` jskumari at gcc dot gnu.org
2023-03-02 12:42 ` jskumari at gcc dot gnu.org
2023-03-02 13:26 ` segher at gcc dot gnu.org
2023-03-03 6:02 ` jskumari 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-106770-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).