From: Michael Meissner <meissner@linux.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
will schmidt <will_schmidt@vnet.ibm.com>,
gcc-patches@gcc.gnu.org,
Segher Boessenkool <segher@kernel.crashing.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH] Generate XXSPLTIDP on power10.
Date: Thu, 26 Aug 2021 22:21:21 -0400 [thread overview]
Message-ID: <YShMIWhiYs7kY5lG@toto.the-meissners.org> (raw)
In-Reply-To: <YSgHiqMxlf/EQYHz@toto.the-meissners.org>
On Thu, Aug 26, 2021 at 05:28:42PM -0400, Michael Meissner wrote:
> I have patches for adding XXSPLTI32DX, but so far, I'm not sure whether it is a
> win or not. This has the xxsplti32dx_operand predicate and the
> xxsplti32dx_constant_p internal function and a separate constraint ("eD") for
> matching it. If xxspltidp_constant_p returns false, then xxsplti32dx_operand
> and xxsplti32dx_constant_p return false. I.e. it only returns true if we
> should use XXSPLTI32DX instead of some other instruction.
Whoops in re-reading that paragraph, I mixed up the return value. The sentence
should have read:
If xxspltidp_constant_p (and xxspltidp_operand) returns "true" then
xxsplti32dx_constant_p (and xxsplti32dx_operand) would return false.
--
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 prev parent reply other threads:[~2021-08-27 2:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 19:46 Michael Meissner
2021-08-26 19:17 ` will schmidt
2021-08-26 21:28 ` Michael Meissner
2021-08-27 2:21 ` Michael Meissner [this message]
2021-08-31 22:52 ` Segher Boessenkool
2021-09-01 20:06 ` Michael Meissner
2021-08-31 14:50 ` Ping: " Michael Meissner
2021-08-31 23:41 ` Segher Boessenkool
2021-09-01 20:22 ` Michael Meissner
2021-09-02 18:38 ` Segher Boessenkool
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=YShMIWhiYs7kY5lG@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).