built-in FFTW3 integration

Jules Bergmann jules at codesourcery.com
Tue Dec 20 18:48:41 UTC 2005


Nathan,

Refresh my memory, why do we need to regenerate configure for FFTW3? 
Fixing up the loose ends in your patch, it works fine with the upstream 
FFTW3 configure.  I tested locally (i686) and on Setha (x86-64).  I had 
to disable the use of SIMD on sethra do to the following errors when 
compiling FFTW3:

gcc -DHAVE_CONFIG_H -I. -I../../fftw-3.0.1/simd -I.. 
-I../../fftw-3.0.1/kernel -O3 -fomit-frame-pointer -fno-schedule-insns 
-fstrict-aliasing -mpreferred-stack-boundary=4 -msse -MT sse.lo -MD -MP 
-MF .deps/sse.Tpo -c ../../fftw-3.0.1/simd/sse.c -o sse.o
/tmp/cckBDFeA.s: Assembler messages:
/tmp/cckBDFeA.s:83: Error: suffix or operands invalid for `push'
/tmp/cckBDFeA.s:85: Error: suffix or operands invalid for `pop'

I see the same errors when configuring/compiling FFTW3 outside of 
VSIPL++.  Once we figure out how to fix these, we can re-enable SIMD for 
x86-64.

Below are the changes relative to the patch you posted.  I did not apply 
the results of re-running FFTW3's bootstrap.

Patch applied.

				-- Jules


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: fftw-patch-patch.diff
URL: <http://sourcerytools.com/pipermail/vsipl++/attachments/20051220/c49c1cd3/attachment.ksh>


More information about the vsipl++ mailing list