Chris@10: Chris@10:
Chris@10:Chris@10: Next: Fortran Examples, Chris@10: Previous: FFTW Constants in Fortran, Chris@10: Up: Calling FFTW from Legacy Fortran Chris@10:
In C, in order to use a plan, one normally calls fftw_execute
,
Chris@10: which executes the plan to perform the transform on the input/output
Chris@10: arrays passed when the plan was created (see Using Plans). The
Chris@10: corresponding subroutine call in legacy Fortran is:
Chris@10:
call dfftw_execute(plan) Chris@10:Chris@10:
Chris@10: However, we have had reports that this causes problems with some
Chris@10: recent optimizing Fortran compilers. The problem is, because the
Chris@10: input/output arrays are not passed as explicit arguments to
Chris@10: dfftw_execute
, the semantics of Fortran (unlike C) allow the
Chris@10: compiler to assume that the input/output arrays are not changed by
Chris@10: dfftw_execute
. As a consequence, certain compilers end up
Chris@10: optimizing out or repositioning the call to dfftw_execute
,
Chris@10: assuming incorrectly that it does nothing.
Chris@10:
Chris@10:
There are various workarounds to this, but the safest and simplest
Chris@10: thing is to not use dfftw_execute
in Fortran. Instead, use the
Chris@10: functions described in New-array Execute Functions, which take
Chris@10: the input/output arrays as explicit arguments. For example, if the
Chris@10: plan is for a complex-data DFT and was created for the arrays
Chris@10: in
and out
, you would do:
Chris@10:
call dfftw_execute_dft(plan, in, out) Chris@10:Chris@10:
Chris@10: There are a few things to be careful of, however: Chris@10: Chris@10:
dfftw_execute_dft
, Real-input (r2c) DFT plans should use use
Chris@10: dfftw_execute_dft_r2c
, and real-output (c2r) DFT plans should
Chris@10: use dfftw_execute_dft_c2r
. The various r2r plans should use
Chris@10: dfftw_execute_r2r
.
Chris@10:
Chris@10: fftw_malloc
in C). You
Chris@10: can, of course, use the FFTW_UNALIGNED
flag when creating the
Chris@10: plan, in which case the plan does not depend on the alignment, but
Chris@10: this may sacrifice substantial performance on architectures (like x86)
Chris@10: with SIMD instructions (see SIMD alignment and fftw_malloc).
Chris@10:
Chris@10: