This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Use of check_vect() in vectorizer testsuite
On Thu, Jun 09, 2005 at 08:29:21AM -0700, Devang Patel wrote:
>
> On Jun 9, 2005, at 8:24 AM, Giovanni Bajo wrote:
>
> >So, the point is that you cannot select between compile-time/run-
> >time based
> >on a target triplet check, at least for this target. What do you
> >suggest?
> >All the other tests use check_vect() exactly for this reason, as
> >far as I
> >can see, so it looks to me that the sensible thing to do is to use
> >check_vect there as well.
>
> hmm.. that means all tests need to use check_vect(). I am going offline
> now for the day, however consult with Dorit and/or Janis and feel free
> to update these tests appropriately for your platform.
The vect tests use 'run' or 'compile' as the dg-do action based on
checks in vect.exp. For powerpc and alpha this is based on a check
of whether hardware support is available, via check_vmx_hw_available
and check_alpha_max_hw_available. A few tests use check_vect at
runtime instead because of limitations of the test directives.
It sounds as if there should be a check in target-supports.exp for
SSE2 support that determines whether the default test action is 'run'
or 'compile' for i686 targets.
Janis