http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58508

--- Comment #7 from Cong Hou <congh at google dot com> ---
OK. I made a new patch to fix this problem. Waiting to be approved.


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  <co...@google.com>
+
+       * gcc.dg/vect/pr58508.c: Update.
+
 2013-10-15  Cong Hou  <co...@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" } */





On Tue, Oct 29, 2013 at 6:50 AM, bernd.edlinger at hotmail dot de
<gcc-bugzi...@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58508
>
> --- Comment #6 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
> (In reply to Cong Hou from comment #5)
>> I guess I should add
>>
>> /* { dg-require-effective-target vect_int } */
>>
>> to the test case. It is right?
>
> Yes.
>
> --
> You are receiving this mail because:
> You reported the bug.

Reply via email to