From: Segher Boessenkool <segher@kernel.crashing.org>
To: Carl Love <cel@us.ibm.com>
Cc: gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH, rs6000] vec_mule and vec_mulo builtin fix
Date: Fri, 21 Jul 2017 20:43:00 -0000 [thread overview]
Message-ID: <20170721204321.GH13471@gate.crashing.org> (raw)
In-Reply-To: <1500591361.19855.44.camel@us.ibm.com>
On Thu, Jul 20, 2017 at 03:56:01PM -0700, Carl Love wrote:
> The following patch is a reworked patch to fix the bugs in the vec_mule
> and vec_mulo patch that had to be reverted. The reverted fix, added the
> correct mule and mulo instructions with vectorization. The
> vectorization support resulted in vectorization in several testcases to
> fail. This patch adds the correct instructions for the vec_mule and
> vec_mulo builtins without vectorization. The goal is add the
> vectorization support again in a future patch.
The patch looks fine to me, but so did the previous version... What
has changed? It's not clear to me.
Segher
next parent reply other threads:[~2017-07-21 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1500591361.19855.44.camel@us.ibm.com>
2017-07-21 20:43 ` Segher Boessenkool [this message]
2017-07-21 21:15 ` 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=20170721204321.GH13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=cel@us.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).