From: Segher Boessenkool <segher@kernel.crashing.org>
To: Will Schmidt <will_schmidt@vnet.ibm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, rs6000] Update vec_splat references in testcases for validity. (pass2)
Date: Tue, 25 Sep 2018 17:58:00 -0000 [thread overview]
Message-ID: <20180925171014.GL23155@gate.crashing.org> (raw)
In-Reply-To: <1537890445.17188.4.camel@brimstone.rchland.ibm.com>
Hi Will,
On Tue, Sep 25, 2018 at 10:47:25AM -0500, Will Schmidt wrote:
> [v2 updates]
> Added the -longlong testcase changes.
> Add 'lxv' to expected instruction list (for power9 targets).
> Update and simplify some commentary sprinkled through the tests.
>
> OK for trunk?
It is still okay afaics. Thanks!
Segher
prev parent reply other threads:[~2018-09-25 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 18:57 [PATCH, rs6000] Update vec_splat references in testcases for validity Will Schmidt
2018-09-21 14:36 ` Segher Boessenkool
2018-09-25 15:47 ` [PATCH, rs6000] Update vec_splat references in testcases for validity. (pass2) Will Schmidt
2018-09-25 17:58 ` Segher Boessenkool [this message]
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=20180925171014.GL23155@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=will_schmidt@vnet.ibm.com \
--cc=wschmidt@linux.vnet.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).