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, testsuite]: Add -mprefer-avx128 to DEFAULT_VECTCFLAGS


On Mon, 9 May 2011, H.J. Lu wrote:

> > Index: lib/target-supports.exp
> > ===================================================================
> > --- lib/target-supports.exp ? ? (revision 173569)
> > +++ lib/target-supports.exp ? ? (working copy)
> > @@ -3845,6 +3845,8 @@
> > ? ? ? ? set dg-do-what-default run
> > ? ? } elseif { [istarget "i?86-*-*"] || [istarget "x86_64-*-*"] } {
> > ? ? ? ? lappend DEFAULT_VECTCFLAGS "-msse2"
> > + ? ? ? # FIXME: Vectorizer testsuite assumes 128bit vector widths.
> > + ? ? ? lappend DEFAULT_VECTCFLAGS "-mprefer-avx128"
> > ? ? ? ? if { [check_effective_target_sse2_runtime] } {
> > ? ? ? ? ? ? set dg-do-what-default run
> > ? ? ? ? } else {
> >
> 
> That means 256bit vectorizer won't be tested. I think we
> should investigate each testcase and update it if needed.

I think we should work out how to get the various vectorizer testsuites to 
run multiple times, with each vector ISA variant that's available on the 
target architecture (so you'd test SSE; 128-bit AVX; 256-bit AVX; and 
maybe other variants - each variant tested with execution testing if 
there's hardware support, compile testing otherwise), like the torture 
testsuites run each test multiple times with different options.  Though 
that certainly complicates all the effective target tests for 
vectorization support, since the results may depend on the options as well 
as the target.

-- 
Joseph S. Myers
joseph@codesourcery.com

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