[vsipl++] [patch] Some enhancements to the FFT code.
Stefan Seefeld
stefan at codesourcery.com
Mon Feb 27 15:10:00 UTC 2006
Jules Bergmann wrote:
> I'm not sure if the mercury FFTs have any stated alignment requirements
> for their temporary buffer, but to be safe we should allocate with
> either a 16-byte (altivec) or 32-byte (cache line) alignment using the
> alloc_aligned function.
Ok, I use alloc_align(32, ...) for now. (Various backends may have their
own optimized memory management routines, so this has to be revisited later.)
I took the occasion to apply a patch to the alloc_align function which
we had discussed many moons ago. It is now parametrized, i.e. instead of
double *array = static_cast<double *>(alloc_align(32, 1024 * sizeof(double)));
you simply write
double *array = alloc_align<double>(32, 1024);
I adjusted all the code that uses alloc_align accordingly (and fixed a
long-standing issue with paths in some sarsim-related scripts). The attached
patch is checked in.
Regards,
Stefan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch
URL: <http://sourcerytools.com/pipermail/vsipl++/attachments/20060227/d3b15473/attachment.ksh>
More information about the vsipl++
mailing list