This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: altivec testcase
> I think this should probably check for powerpc-* or rs6000-* triplet
> too, but otherwise it seems OK.
ok, my last one didn't actually work correctly because CFLAGS does not
contain -maltivec.
i'm not sure what the correct solution is here. i want to make sure
xgcc is being called with -maltivec, and only then run the testsuite.
for a cross build, the patch below is working. calling target_info and
board_info seems to be the only way to get at those flags. but i'm not
sure what the correct approach would be for native.
i suppose eventually we can check for powerpc-*-*altivec when i add the
triplets.
but i'm holding off checking in until i get some suggestions :)
aldy
Index: altivec.x
===================================================================
RCS file: altivec.x
diff -N altivec.x
*** /dev/null Tue May 5 13:32:27 1998
--- altivec.x Sat Nov 17 07:33:30 2001
***************
*** 0 ****
--- 1,11 ----
+ # This test is only needed for rs6000 with -maltivec
+
+ set dest [target_info name]
+ set flags [board_info $dest multilib_flags]
+
+ if { (![istarget "rs6000-*-*"] && ![istarget "powerpc-*-*"])
+ || ![string match "*maltivec*" $flags]} {
+ return 1
+ }
+
+ return 0