altivec testcase

Geoff Keating geoffk@geoffk.org
Tue Nov 13 15:03:00 GMT 2001


Aldy Hernandez <aldyh@redhat.com> writes:

> hi guys.
> 
> i've gotten several emails asking how to use what we currently have for
> altivec.  i think it's time to add a testcase.
> 
> this test should obviously only be run for -maltivec.  i'd like to add
> altivec.x and altivec.c.  is this the right way to do it?
> 
> eventually i'd like to replace this test with a more in depth one using
> the upcoming overloaded vec_blah() functions.  it will for sure make it
> more readable (not that builtins are supposed to be readable :)).
> 
> i've tested this case on actual hardware and it works :)
> 
> is this ok?
> 
> 2001-11-16  Aldy Hernandez  <aldyh@redhat.com>
> 
>         * gcc.c-torture/execute/altivec.c: New.
> 	
>         * gcc.c-torture/execute/altivec.x: New.
> 
...
> + # This test is only needed for rs6000 with -maltivec
> + 
> + if { ! [string match "*maltivec*" $CFLAGS] } { return 1 }
> + return 0

I think this should probably check for powerpc-* or rs6000-* triplet
too, but otherwise it seems OK.

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>



More information about the Gcc-patches mailing list