This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Vectorizer testsuite adjustments for P7


Hello!

> The attached patch includes vectorizer testsuite adjustments for P7.
> Tested on P7.
>
>        * gcc.target/powerpc/vsx-vectorize-8.c: New test.
>        * gcc.target/powerpc/vsx-vectorize-1.c: Likewise.
>        * gcc.target/powerpc/vsx-vectorize-2.c: Likewise.
>        * gcc.target/powerpc/vsx-vectorize-3.c: Likewise.
>        * gcc.target/powerpc/vsx-vectorize-4.c: Likewise.
>        * gcc.target/powerpc/vsx-vectorize-5.c: Likewise.
>        * gcc.target/powerpc/vsx-vectorize-6.c: Likewise.
>        * gcc.target/powerpc/vsx-vectorize-7.c: Likewise.
>        * gcc.dg/vect/vect.exp: Add Power7 flags.

> Index: gcc.dg/vect/vect.exp
> ===================================================================
> --- gcc.dg/vect/vect.exp	(revision 151914)
> +++ gcc.dg/vect/vect.exp	(working copy)
> @@ -51,6 +51,10 @@ if  [istarget "powerpc-*paired*"]  {
>      }
>
>      lappend DEFAULT_VECTCFLAGS "-maltivec"
> +    if [check_vsx_hw_available]  {
> +      lappend DEFAULT_VECTCFLAGS "-mvsx" "-mno-allow-movmisalign"
> +    }
> +
>      if [check_vmx_hw_available] {
>  	set dg-do-what-default run
>      } else {

You should also update g++.dg/vect/vect.exp and
gfortran.dg/vect/vect.exp with the same change.

It would be even better to separate common code into support function
and use this function instead. Three copies of the same code in each
vect.exp file look like maintenance nightmare to me...

Uros.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]