> Give it a shot. Note that the fft transforms also use int instead of > intp, > which limits the maximum transform size to 32 bits. Fixing that is > somewhere > on my todo list but I would be happy to leave it to you ;) Although I > expect > transforms > 2GB aren't all that common.
By the way... When looking at fftpack.c there are two things that would likely improve the performance. 1) If we used ISO C (aka C99), arrays could be restricted, thus allowing more aggressive optimization. Now the compiler has to assume aliasing between function arguments. But as the C code is translated from Fortran, this is not the case. 2) In C, indexing arrays with unsigned integers are much more efficient (cf. AMDs optimization guide). I think the use of signed integers as array indices are inherited from Fortran77 FFTPACK. We should probably index the arrays with unsigned longs. Sturla Molden _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
