public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	       Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Re: [PATCH 1/3][rs6000] Replace vsx_xvcdpsp by vsx_xvcvdpsp
Date: Wed, 30 Oct 2019 18:02:00 -0000	[thread overview]
Message-ID: <20191030175738.GK28442@gate.crashing.org> (raw)
In-Reply-To: <8c4cac65-7faf-74ec-e008-56ccfdf6e8ca@linux.ibm.com>

Hi!

On Wed, Oct 23, 2019 at 05:39:14PM +0800, Kewen.Lin wrote:
> I noticed that vsx_xvcdpsp and vsx_xvcvdpsp are almost the same,
> and vsx_xvcdpsp looks replaceable with vsx_xvcvdpsp since it's only
> called by gen_*.

Okay for trunk.  Thanks!


Segher


> 2019-10-23  Kewen Lin  <linkw@gcc.gnu.org>
> 
> 	* config/rs6000/vsx.md (vsx_xvcdpsp): Remove define_insn.
> 	(UNSPEC_VSX_XVCDPSP): Remove.
> 	* config/rs6000/rs6000.c (rs6000_generate_float2_double_code):
> 	Replace gen_vsx_xvcdpsp by gen_vsx_xvcvdpsp.

  reply	other threads:[~2019-10-30 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  9:39 [PATCH 0/3][rs6000] Update RTL patterns for vector conversion Kewen.Lin
2019-10-23  9:40 ` [PATCH 1/3][rs6000] Replace vsx_xvcdpsp by vsx_xvcvdpsp Kewen.Lin
2019-10-30 18:02   ` Segher Boessenkool [this message]
2019-10-23  9:42 ` [PATCH 2/3][rs6000] vector conversion RTL pattern update for same unit size Kewen.Lin
2019-10-30 18:04   ` Segher Boessenkool
2019-10-23 10:15 ` [PATCH 3/3][rs6000] vector conversion RTL pattern update for diff " Kewen.Lin
2019-10-30 19:06   ` Segher Boessenkool
2019-10-31  9:35     ` [PATCH 3/3 V2][rs6000] " Kewen.Lin
2019-10-31 18:54       ` Segher Boessenkool
2019-11-01  2:21         ` Kewen.Lin

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=20191030175738.GK28442@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linkw@linux.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).