Use of check_vect() in vectorizer testsuite

[Devang Patel]

On Jun 9, 2005, at 3:29 AM, Giovanni Bajo wrote:

> Hello,
>
> I have some questions about the use of check_vect() in the vectorizer
> testsuite:
>
> 1) All the ifcvt tests (vect-ifcvt*) seem to require SSE2  
> capability to be
> vectorized but they do not call check_vect(). Is this a bug? They  
> surely fail
> on my platform (which does not have SSE2).
>
> 2) The same applies for a vect_int test, vect-dv-2.c. I assume also  
> vect_int
> tests require SSE2 capability and thus should call check_vect()?


check_vect() is used to test whether to run the test or not. Now,  
vect.exp
does the job more efficiently.

      29 # If the target system supports vector instructions, the  
default action
      30 # for a test is 'run', otherwise it's 'compile'.  Save  
current default.
      31 # Executing vector instructions on a system without hardware  
vector support
      32 # is also disabled by a call to check_vect, but disabling  
execution here is
      33 # more efficient.


And dg-require-... should control whether this test should be enabled  
or not.
So depending upon the failure (runtime or compiler not vectorizing  
loops),
you want to update appropriate code block in vect.exp for your platform.

-
Devang