From: Cong Hou <congh@google.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Small fix: add { dg-require-effective-target vect_int } to testsuite/gcc.dg/vect/pr58508.c
Date: Fri, 08 Nov 2013 05:46:00 -0000 [thread overview]
Message-ID: <CAK=A3=224PREHivMNu-ONqm3qVDGxuHzYEDyK=ULGNXw7hJ43w@mail.gmail.com> (raw)
In-Reply-To: <CAK=A3=3gdYEXHdvpKCejEKXGKHqqCCLzbFbHQdPcGRYjs9uOWA@mail.gmail.com>
Ping. OK for the trunk?
thanks,
Cong
On Fri, Nov 1, 2013 at 10:47 AM, Cong Hou <congh@google.com> wrote:
> It seems that on some platforms the loops in
> testsuite/gcc.dg/vect/pr58508.c may be unable to be vectorized. This
> small patch added { dg-require-effective-target vect_int } to make
> sure all loops can be vectorized.
>
>
> thanks,
> Cong
>
>
> diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
> index 9d0f4a5..3d9916d 100644
> --- a/gcc/testsuite/ChangeLog
> +++ b/gcc/testsuite/ChangeLog
> @@ -1,3 +1,7 @@
> +2013-10-29 Cong Hou <congh@google.com>
> +
> + * gcc.dg/vect/pr58508.c: Update.
> +
> 2013-10-15 Cong Hou <congh@google.com>
>
> * gcc.dg/vect/pr58508.c: New test.
> diff --git a/gcc/testsuite/gcc.dg/vect/pr58508.c
> b/gcc/testsuite/gcc.dg/vect/pr58508.c
> index 6484a65..fff7a04 100644
> --- a/gcc/testsuite/gcc.dg/vect/pr58508.c
> +++ b/gcc/testsuite/gcc.dg/vect/pr58508.c
> @@ -1,3 +1,4 @@
> +/* { dg-require-effective-target vect_int } */
> /* { dg-do compile } */
> /* { dg-options "-O2 -ftree-vectorize -fdump-tree-vect-details" } */
next prev parent reply other threads:[~2013-11-08 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 17:47 Cong Hou
2013-11-08 5:46 ` Cong Hou [this message]
2013-11-08 10:09 ` Richard Biener
2013-11-12 15:14 ` Jakub Jelinek
2013-11-12 18:26 ` Cong Hou
2013-11-12 18:34 ` Jakub Jelinek
2013-11-12 18:47 ` Cong Hou
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='CAK=A3=224PREHivMNu-ONqm3qVDGxuHzYEDyK=ULGNXw7hJ43w@mail.gmail.com' \
--to=congh@google.com \
--cc=gcc-patches@gcc.gnu.org \
/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).