[vsipl++] [patch] Re: [patch] SSE on amd64, other config hax

[Jules Bergmann]

Nathan (Jasper) Myers wrote:
> On Tue, Dec 20, 2005 at 11:38:23PM -0800, Nathan (Jasper) Myers wrote:
> 
>>On Wed, Dec 21, 2005 at 12:13:15AM -0500, Jules Bergmann wrote:
>>
>>>Nathan (Jasper) Myers wrote:
>>>
>>>>Patch below makes FFTW3 use SSE/SSE2 on x86-64, and cleans up some
>>>>config file and minor build details.  OK?
>>>
>>>Looks good, please check it in.  Do the x86-64 changes work on Sethra? 
>>
>>Hmm, on cugel, built with /home/jules/local/x86_64/gcc-4.0.1/bin/g++ ...
>>
>>qmtest run fft.cpp   PASS
>>qmtest run fftm.cpp  FAIL

Good thing I asked!

> 
> 
> When built with /usr/local/tools/gcc-3.4.0/bin/g++ and tested using 
> /home/jules/local/x86_64/bin/qmtest, both PASS.

Good, that is the compiler we're most worried about (and the Sourcery 
G++ packaged version of it).

> 
> (BTW, when tested using /usr/local/tools/gcc-3.4.0/bin/qmtest, 
> all tests fail with 'The context variable "CompilerTable.compiler_table" 
> was not defined.'  Evidently the qmtest installed there is obsolete.)

You should be pulling qmtest out of /usr/local/tools/vpp-1.0/bin.  If 
you source /usr/local/tools/vpp-1.0/vars.sh, it will set your path up 
for you.

> 
> New patch below.  I tried to check it in, from both cugel and sethra,
> but just get "cvs commit: Up-to-date check failed for" Changelog,
> configure.ac, and GNUmakefile.in, despite that I have just cvs-updated
> them; and then deleted, cvs-updated, and re-patched them.  Are the
> timestamps on CVS's files messed up?

Don't know whats causing that.  I will tests the patch and then apply it 
for you.  I'm going to leave out the questionable bits below.


>  
>  vendor_FFTW_LIBS := \
> -	vendor/fftw3f/libfftw3f-csl.a \
> -	vendor/fftw3/libfftw3-csl.a \
> -	vendor/fftw3l/libfftw3l-csl.a \
> +	vendor/fftw3f/.libs/libfftw3f-csl.a \
> +	vendor/fftw3/.libs/libfftw3-csl.a \
> +	vendor/fftw3l/.libs/libfftw3l-csl.a

If you change the locations of the libraries, don't you also need to 
change the soft links created by configure?

>  
>  all:: $(vendor_FFTW_LIBS)
>  
>  libs:: $(vendor_FFTW_LIBS)
>  
> -vendor/fftw3f/libfftw3f-csl.a:
> -	@echo "Building FFTW float (fftw-f.build.log)"
> +vendor/fftw3f/.libs/libfftw3f-csl.a:
> +	@echo "Building FFTW float (see fftw-f.build.log)"
>  	@$(MAKE) -C vendor/fftw3f > fftw-f.build.log 2>&1
> -	mv vendor/fftw3f/.libs/libfftw3f.a vendor/fftw3f/libfftw3f-csl.a

Does this actually work?  When building FFTW3, I see it ignoring the 
"-csl" suffix passed at configure.  Hence the move from 
'vendor/fftw3f/.libs/libfftw3f.a'.  Likewise for libfftw3.a and libfftw3l.a.

				-- Jules