public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [testsuite, committed] Fix effective target for ivdep tests
Date: Mon, 10 Feb 2014 11:09:00 -0000	[thread overview]
Message-ID: <60535293.dz4Md6dapA@polaris> (raw)
In-Reply-To: <87ppn9badi.fsf@talisman.default>

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

> The ivdep tests use int arrays but required vect_float rather than vect_int.
> 
> Tested on mipsisa64-sde-elf, where it fixes some spurious failures for
> -mips32r2/-mfp64, and on mips64-linux-gnu.  Applied as obvious.

The 3rd and 4th tests also require vect_int_mult.

Tested on x86-64/Linux and SPARC/Solaris, applied on the mainline as obvious.


2014-02-10  Eric Botcazou  <ebotcazou@adacore.com>

	* g++.dg/vect/pr33426-ivdep-3.cc: Require vect_int_mult as well.
	* g++.dg/vect/pr33426-ivdep-4.cc: Likewise.


-- 
Eric Botcazou

[-- Attachment #2: p.diff --]
[-- Type: text/x-patch, Size: 979 bytes --]

Index: g++.dg/vect/pr33426-ivdep-4.cc
===================================================================
--- g++.dg/vect/pr33426-ivdep-4.cc	(revision 207641)
+++ g++.dg/vect/pr33426-ivdep-4.cc	(working copy)
@@ -1,5 +1,6 @@
 /* { dg-do compile } */
 /* { dg-require-effective-target vect_int } */
+/* { dg-require-effective-target vect_int_mult } */
 /* { dg-additional-options "-std=c++11 -O3 -fopt-info-vec-optimized -fdump-tree-original -fdump-tree-gimple" } */
 
 /* PR other/33426 */
Index: g++.dg/vect/pr33426-ivdep-3.cc
===================================================================
--- g++.dg/vect/pr33426-ivdep-3.cc	(revision 207641)
+++ g++.dg/vect/pr33426-ivdep-3.cc	(working copy)
@@ -1,5 +1,6 @@
 /* { dg-do compile } */
 /* { dg-require-effective-target vect_int } */
+/* { dg-require-effective-target vect_int_mult } */
 /* { dg-additional-options "-std=c++11 -O3 -fopt-info-vec-optimized -fdump-tree-original -fdump-tree-gimple" } */
 
 /* PR other/33426 */

      reply	other threads:[~2014-02-10 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 18:19 Richard Sandiford
2014-02-10 11:09 ` Eric Botcazou [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=60535293.dz4Md6dapA@polaris \
    --to=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdsandiford@googlemail.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).