Mercurial > hg > js-dsp-test

annotate fft/fftw/fftw-3.3.4/doc/html/Plan-execution-in-Fortran.html @ 40:223f770b5341 kissfft-double tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Try a double-precision kissfft
author Chris Cannam
date Wed, 07 Sep 2016 10:40:32 +0100
parents 26056e866c29
children
rev   line source
Chris@19 1 <html lang="en">
Chris@19 2 <head>
Chris@19 3 <title>Plan execution in Fortran - FFTW 3.3.4</title>
Chris@19 4 <meta http-equiv="Content-Type" content="text/html">
Chris@19 5 <meta name="description" content="FFTW 3.3.4">
Chris@19 6 <meta name="generator" content="makeinfo 4.13">
Chris@19 7 <link title="Top" rel="start" href="index.html#Top">
Chris@19 8 <link rel="up" href="Calling-FFTW-from-Modern-Fortran.html#Calling-FFTW-from-Modern-Fortran" title="Calling FFTW from Modern Fortran">
Chris@19 9 <link rel="prev" href="FFTW-Fortran-type-reference.html#FFTW-Fortran-type-reference" title="FFTW Fortran type reference">
Chris@19 10 <link rel="next" href="Allocating-aligned-memory-in-Fortran.html#Allocating-aligned-memory-in-Fortran" title="Allocating aligned memory in Fortran">
Chris@19 11 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
Chris@19 12 <!--
Chris@19 13 This manual is for FFTW
Chris@19 14 (version 3.3.4, 20 September 2013).
Chris@19 15
Chris@19 16 Copyright (C) 2003 Matteo Frigo.
Chris@19 17
Chris@19 18 Copyright (C) 2003 Massachusetts Institute of Technology.
Chris@19 19
Chris@19 20 Permission is granted to make and distribute verbatim copies of
Chris@19 21 this manual provided the copyright notice and this permission
Chris@19 22 notice are preserved on all copies.
Chris@19 23
Chris@19 24 Permission is granted to copy and distribute modified versions of
Chris@19 25 this manual under the conditions for verbatim copying, provided
Chris@19 26 that the entire resulting derived work is distributed under the
Chris@19 27 terms of a permission notice identical to this one.
Chris@19 28
Chris@19 29 Permission is granted to copy and distribute translations of this
Chris@19 30 manual into another language, under the above conditions for
Chris@19 31 modified versions, except that this permission notice may be
Chris@19 32 stated in a translation approved by the Free Software Foundation.
Chris@19 33 -->
Chris@19 34 <meta http-equiv="Content-Style-Type" content="text/css">
Chris@19 35 <style type="text/css"><!--
Chris@19 36 pre.display { font-family:inherit }
Chris@19 37 pre.format { font-family:inherit }
Chris@19 38 pre.smalldisplay { font-family:inherit; font-size:smaller }
Chris@19 39 pre.smallformat { font-family:inherit; font-size:smaller }
Chris@19 40 pre.smallexample { font-size:smaller }
Chris@19 41 pre.smalllisp { font-size:smaller }
Chris@19 42 span.sc { font-variant:small-caps }
Chris@19 43 span.roman { font-family:serif; font-weight:normal; }
Chris@19 44 span.sansserif { font-family:sans-serif; font-weight:normal; }
Chris@19 45 --></style>
Chris@19 46 </head>
Chris@19 47 <body>
Chris@19 48 <div class="node">
Chris@19 49 <a name="Plan-execution-in-Fortran"></a>
Chris@19 50 <p>
Chris@19 51 Next:&nbsp;<a rel="next" accesskey="n" href="Allocating-aligned-memory-in-Fortran.html#Allocating-aligned-memory-in-Fortran">Allocating aligned memory in Fortran</a>,
Chris@19 52 Previous:&nbsp;<a rel="previous" accesskey="p" href="FFTW-Fortran-type-reference.html#FFTW-Fortran-type-reference">FFTW Fortran type reference</a>,
Chris@19 53 Up:&nbsp;<a rel="up" accesskey="u" href="Calling-FFTW-from-Modern-Fortran.html#Calling-FFTW-from-Modern-Fortran">Calling FFTW from Modern Fortran</a>
Chris@19 54 <hr>
Chris@19 55 </div>
Chris@19 56
Chris@19 57 <h3 class="section">7.4 Plan execution in Fortran</h3>
Chris@19 58
Chris@19 59 <p>In C, in order to use a plan, one normally calls <code>fftw_execute</code>,
Chris@19 60 which executes the plan to perform the transform on the input/output
Chris@19 61 arrays passed when the plan was created (see <a href="Using-Plans.html#Using-Plans">Using Plans</a>). The
Chris@19 62 corresponding subroutine call in modern Fortran is:
Chris@19 63 <pre class="example"> call fftw_execute(plan)
Chris@19 64 </pre>
Chris@19 65 <p><a name="index-fftw_005fexecute-557"></a>
Chris@19 66 However, we have had reports that this causes problems with some
Chris@19 67 recent optimizing Fortran compilers. The problem is, because the
Chris@19 68 input/output arrays are not passed as explicit arguments to
Chris@19 69 <code>fftw_execute</code>, the semantics of Fortran (unlike C) allow the
Chris@19 70 compiler to assume that the input/output arrays are not changed by
Chris@19 71 <code>fftw_execute</code>. As a consequence, certain compilers end up
Chris@19 72 repositioning the call to <code>fftw_execute</code>, assuming incorrectly
Chris@19 73 that it does nothing to the arrays.
Chris@19 74
Chris@19 75 <p>There are various workarounds to this, but the safest and simplest
Chris@19 76 thing is to not use <code>fftw_execute</code> in Fortran. Instead, use the
Chris@19 77 functions described in <a href="New_002darray-Execute-Functions.html#New_002darray-Execute-Functions">New-array Execute Functions</a>, which take
Chris@19 78 the input/output arrays as explicit arguments. For example, if the
Chris@19 79 plan is for a complex-data DFT and was created for the arrays
Chris@19 80 <code>in</code> and <code>out</code>, you would do:
Chris@19 81 <pre class="example"> call fftw_execute_dft(plan, in, out)
Chris@19 82 </pre>
Chris@19 83 <p><a name="index-fftw_005fexecute_005fdft-558"></a>
Chris@19 84 There are a few things to be careful of, however:
Chris@19 85
Chris@19 86 <ul>
Chris@19 87 <li><a name="index-fftw_005fexecute_005fdft_005fr2c-559"></a><a name="index-fftw_005fexecute_005fdft_005fc2r-560"></a><a name="index-fftw_005fexecute_005fr2r-561"></a>You must use the correct type of execute function, matching the way
Chris@19 88 the plan was created. Complex DFT plans should use
Chris@19 89 <code>fftw_execute_dft</code>, Real-input (r2c) DFT plans should use use
Chris@19 90 <code>fftw_execute_dft_r2c</code>, and real-output (c2r) DFT plans should
Chris@19 91 use <code>fftw_execute_dft_c2r</code>. The various r2r plans should use
Chris@19 92 <code>fftw_execute_r2r</code>. Fortunately, if you use the wrong one you
Chris@19 93 will get a compile-time type-mismatch error (unlike legacy Fortran).
Chris@19 94
Chris@19 95 <li>You should normally pass the same input/output arrays that were used when
Chris@19 96 creating the plan. This is always safe.
Chris@19 97
Chris@19 98 <li><em>If</em> you pass <em>different</em> input/output arrays compared to
Chris@19 99 those used when creating the plan, you must abide by all the
Chris@19 100 restrictions of the new-array execute functions (see <a href="New_002darray-Execute-Functions.html#New_002darray-Execute-Functions">New-array Execute Functions</a>). The most tricky of these is the
Chris@19 101 requirement that the new arrays have the same alignment as the
Chris@19 102 original arrays; the best (and possibly only) way to guarantee this
Chris@19 103 is to use the &lsquo;<samp><span class="samp">fftw_alloc</span></samp>&rsquo; functions to allocate your arrays (see <a href="Allocating-aligned-memory-in-Fortran.html#Allocating-aligned-memory-in-Fortran">Allocating aligned memory in Fortran</a>). Alternatively, you can
Chris@19 104 use the <code>FFTW_UNALIGNED</code> flag when creating the
Chris@19 105 plan, in which case the plan does not depend on the alignment, but
Chris@19 106 this may sacrifice substantial performance on architectures (like x86)
Chris@19 107 with SIMD instructions (see <a href="SIMD-alignment-and-fftw_005fmalloc.html#SIMD-alignment-and-fftw_005fmalloc">SIMD alignment and fftw_malloc</a>).
Chris@19 108 <a name="index-FFTW_005fUNALIGNED-562"></a>
Chris@19 109 </ul>
Chris@19 110
Chris@19 111 <!-- -->
Chris@19 112 </body></html>
Chris@19 113