public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Will Schmidt <will_schmidt@vnet.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] fold-vec-mult* testcase updates for power9
Date: Thu, 22 Feb 2018 17:51:00 -0000	[thread overview]
Message-ID: <20180222175101.GF21977@gate.crashing.org> (raw)
In-Reply-To: <1519234356.11602.369.camel@brimstone.rchland.ibm.com>

Hi!

On Wed, Feb 21, 2018 at 11:32:36AM -0600, Will Schmidt wrote:
> An update for the fold-vec-mult-int128-p9.c test to include more of
> the instructions generated for a vec_mul() with a power9 target.
>     
> [testsuite]
>     
> 2018-02-21  Will Schmidt  <will_schmidt@vnet.ibm.com>
> 
> 	* fold-vec-mult-int128-p9.c: Add maddld insn to expected output.

This is fine for trunk.  Thanks!


Segher


> diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-mult-int128-p9.c b/gcc/testsuite/gcc.target/powerpc/fold-vec-mult-int128-p9.c
> index 6571884..5d3d4aa 100644
> --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-mult-int128-p9.c
> +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-mult-int128-p9.c
> @@ -20,7 +20,7 @@ vector unsigned __int128
>  test2 (vector unsigned __int128 x, vector unsigned __int128 y)
>  {
>    return vec_mul (x, y);
>  }
>  
> -/* { dg-final { scan-assembler-times {\mmulld\M} 4 } } */
> +/* { dg-final { scan-assembler-times {\mmulld\M|\mmaddld\M} 6 } } */
>  /* { dg-final { scan-assembler-times {\mmulhdu\M} 2 } } */
> 

      reply	other threads:[~2018-02-22 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 17:32 Will Schmidt
2018-02-22 17:51 ` 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=20180222175101.GF21977@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).