* expr.c (highest_pow2_factor): Make extern.

[pf3gnuchains/gcc-fork.git] / gcc / testsuite / gcc.dg / vect / vect-91.c

diff --git a/gcc/testsuite/gcc.dg/vect/vect-91.c b/gcc/testsuite/gcc.dg/vect/vect-91.c
index 96099f4..d72bd4c 100644 (file)
--- a/gcc/testsuite/gcc.dg/vect/vect-91.c
+++ b/gcc/testsuite/gcc.dg/vect/vect-91.c
@@ -11,10 +11,7 @@ extern int a[N];
 /* The alignment of 'pa' is unknown. 
    Yet we do know that both the read access and write access have 
    the same alignment. Peeling to align one of the accesses will 
-   align the other.
-
-   Not vectorized yet due to problems in dataref analysis that
-   are fixed in autovect-branch but not yet in mainline.  */
+   align the other.  */
 
 int
 main1 (int * pa)
@@ -60,11 +57,8 @@ main3 ()
   return 0;
 }
 
-/* Currently only the loops in main2 and main3 get vectorized. After the merge 
-   of the datarefs-analysis cleanups from autovect-branch to mainline, the loop
-   in main1 will also be vectorized.  */ 
-/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 2 "vect" { xfail vect_no_int_add } } } */
+/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 3 "vect" } } */
 /* { dg-final { scan-tree-dump-times "Vectorizing an unaligned access" 0 "vect" } } */
-/* { dg-final { scan-tree-dump-times "accesses have the same alignment." 2 "vect" } } */
-/* { dg-final { scan-tree-dump-times "Alignment of access forced using peeling" 2 "vect" } } */
+/* { dg-final { scan-tree-dump-times "accesses have the same alignment." 3 "vect" } } */
+/* { dg-final { scan-tree-dump-times "Alignment of access forced using peeling" 3 "vect" } } */
 /* { dg-final { cleanup-tree-dump "vect" } } */