From: Michael Meissner <meissner@linux.ibm.com>
To: gcc-patches@gcc.gnu.org,
Michael Meissner <meissner@linux.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: [PATCH 0/2] Move xx* builtins to vsx.md.
Date: Tue, 18 May 2021 16:43:07 -0400 [thread overview]
Message-ID: <20210518204307.GA16304@ibm-toto.the-meissners.org> (raw)
[PATCH 0/2] Move xx* builtins to vsx.md.
I noticed that the xx built-in functions (xxspltiw, xxspltidp, xxsplti32dx,
xxeval, xxblend, and xxpermx) were all defined in altivec.md. However, since
the XX instructions can take both traditional floating point and Altivec
registers, these built-in functions should be in vsx.md.
The first patch just moves the insns from altivec.md to vsx.md.
The second patch fixes a predicate error that I noticed when was doing the
error.
I also moved the VM3 mode iterator and VM3_char mode attribute from altivec.md
to vsx.md, since the only use of these were for the XXBLEND insns.
I have bootstraped this on LE power9 and BE power8 systems. There were no
regressions. Can I check this into the trunk?
It does not need to be backported to GCC 11 unless we want to back port the
support for XXSPLTIW, XXSPLTIDP, and XXSPLTI32DX instructions that will be
later patches.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meissner@linux.ibm.com, phone: +1 (978) 899-4797
next reply other threads:[~2021-05-18 20:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 20:43 Michael Meissner [this message]
2021-05-18 20:46 ` [PATCH 1/2] " Michael Meissner
2021-05-20 19:30 ` will schmidt
2021-05-21 1:52 ` Michael Meissner
2021-05-24 15:58 ` Ping " Michael Meissner
2021-05-18 20:47 ` [PATCH 2/2] Fix xxeval predicates Michael Meissner
2021-05-20 19:31 ` will schmidt
2021-05-21 1:53 ` Michael Meissner
2021-05-24 16:02 ` Ping " Michael Meissner
2021-06-02 0:15 ` Michael Meissner
2021-06-02 0:13 ` Ping #2: [PATCH 0/2] Move xx* builtins to vsx.md Michael Meissner
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=20210518204307.GA16304@ibm-toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.ibm.com \
--cc=wschmidt@linux.ibm.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).