Chris@10: Chris@10: Chris@10: SIMD alignment and fftw_malloc - FFTW 3.3.3 Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10: Chris@10:
Chris@10: Chris@10: Chris@10:

Chris@10: Next: , Chris@10: Previous: Other Important Topics, Chris@10: Up: Other Important Topics Chris@10:


Chris@10:
Chris@10: Chris@10:

3.1 SIMD alignment and fftw_malloc

Chris@10: Chris@10:

SIMD, which stands for “Single Instruction Multiple Data,” is a set of Chris@10: special operations supported by some processors to perform a single Chris@10: operation on several numbers (usually 2 or 4) simultaneously. SIMD Chris@10: floating-point instructions are available on several popular CPUs: Chris@10: SSE/SSE2/AVX on recent x86/x86-64 processors, AltiVec (single precision) Chris@10: on some PowerPCs (Apple G4 and higher), NEON on some ARM models, and MIPS Paired Single Chris@10: (currently only in FFTW 3.2.x). FFTW can be compiled to support the Chris@10: SIMD instructions on any of these systems. Chris@10: Chris@10: Chris@10:

A program linking to an FFTW library compiled with SIMD support can Chris@10: obtain a nonnegligible speedup for most complex and r2c/c2r Chris@10: transforms. In order to obtain this speedup, however, the arrays of Chris@10: complex (or real) data passed to FFTW must be specially aligned in Chris@10: memory (typically 16-byte aligned), and often this alignment is more Chris@10: stringent than that provided by the usual malloc (etc.) Chris@10: allocation routines. Chris@10: Chris@10:

In order to guarantee proper alignment for SIMD, therefore, in case Chris@10: your program is ever linked against a SIMD-using FFTW, we recommend Chris@10: allocating your transform data with fftw_malloc and Chris@10: de-allocating it with fftw_free. Chris@10: These have exactly the same interface and behavior as Chris@10: malloc/free, except that for a SIMD FFTW they ensure Chris@10: that the returned pointer has the necessary alignment (by calling Chris@10: memalign or its equivalent on your OS). Chris@10: Chris@10:

You are not required to use fftw_malloc. You can Chris@10: allocate your data in any way that you like, from malloc to Chris@10: new (in C++) to a fixed-size array declaration. If the array Chris@10: happens not to be properly aligned, FFTW will not use the SIMD Chris@10: extensions. Chris@10: Chris@10: Since fftw_malloc only ever needs to be used for real and Chris@10: complex arrays, we provide two convenient wrapper routines Chris@10: fftw_alloc_real(N) and fftw_alloc_complex(N) that are Chris@10: equivalent to (double*)fftw_malloc(sizeof(double) * N) and Chris@10: (fftw_complex*)fftw_malloc(sizeof(fftw_complex) * N), Chris@10: respectively (or their equivalents in other precisions). Chris@10: Chris@10: Chris@10: Chris@10: