Mercurial > hg > sv-dependency-builds
comparison src/fftw-3.3.8/doc/html/Plan-execution-in-Fortran.html @ 167:bd3cc4d1df30
Add FFTW 3.3.8 source, and a Linux build
| author | Chris Cannam <cannam@all-day-breakfast.com> |
|---|---|
| date | Tue, 19 Nov 2019 14:52:55 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 166:cbd6d7e562c7 | 167:bd3cc4d1df30 |
|---|---|
| 1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> | |
| 2 <html> | |
| 3 <!-- This manual is for FFTW | |
| 4 (version 3.3.8, 24 May 2018). | |
| 5 | |
| 6 Copyright (C) 2003 Matteo Frigo. | |
| 7 | |
| 8 Copyright (C) 2003 Massachusetts Institute of Technology. | |
| 9 | |
| 10 Permission is granted to make and distribute verbatim copies of this | |
| 11 manual provided the copyright notice and this permission notice are | |
| 12 preserved on all copies. | |
| 13 | |
| 14 Permission is granted to copy and distribute modified versions of this | |
| 15 manual under the conditions for verbatim copying, provided that the | |
| 16 entire resulting derived work is distributed under the terms of a | |
| 17 permission notice identical to this one. | |
| 18 | |
| 19 Permission is granted to copy and distribute translations of this manual | |
| 20 into another language, under the above conditions for modified versions, | |
| 21 except that this permission notice may be stated in a translation | |
| 22 approved by the Free Software Foundation. --> | |
| 23 <!-- Created by GNU Texinfo 6.3, http://www.gnu.org/software/texinfo/ --> | |
| 24 <head> | |
| 25 <title>FFTW 3.3.8: Plan execution in Fortran</title> | |
| 26 | |
| 27 <meta name="description" content="FFTW 3.3.8: Plan execution in Fortran"> | |
| 28 <meta name="keywords" content="FFTW 3.3.8: Plan execution in Fortran"> | |
| 29 <meta name="resource-type" content="document"> | |
| 30 <meta name="distribution" content="global"> | |
| 31 <meta name="Generator" content="makeinfo"> | |
| 32 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> | |
| 33 <link href="index.html#Top" rel="start" title="Top"> | |
| 34 <link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index"> | |
| 35 <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents"> | |
| 36 <link href="Calling-FFTW-from-Modern-Fortran.html#Calling-FFTW-from-Modern-Fortran" rel="up" title="Calling FFTW from Modern Fortran"> | |
| 37 <link href="Allocating-aligned-memory-in-Fortran.html#Allocating-aligned-memory-in-Fortran" rel="next" title="Allocating aligned memory in Fortran"> | |
| 38 <link href="FFTW-Fortran-type-reference.html#FFTW-Fortran-type-reference" rel="prev" title="FFTW Fortran type reference"> | |
| 39 <style type="text/css"> | |
| 40 <!-- | |
| 41 a.summary-letter {text-decoration: none} | |
| 42 blockquote.indentedblock {margin-right: 0em} | |
| 43 blockquote.smallindentedblock {margin-right: 0em; font-size: smaller} | |
| 44 blockquote.smallquotation {font-size: smaller} | |
| 45 div.display {margin-left: 3.2em} | |
| 46 div.example {margin-left: 3.2em} | |
| 47 div.lisp {margin-left: 3.2em} | |
| 48 div.smalldisplay {margin-left: 3.2em} | |
| 49 div.smallexample {margin-left: 3.2em} | |
| 50 div.smalllisp {margin-left: 3.2em} | |
| 51 kbd {font-style: oblique} | |
| 52 pre.display {font-family: inherit} | |
| 53 pre.format {font-family: inherit} | |
| 54 pre.menu-comment {font-family: serif} | |
| 55 pre.menu-preformatted {font-family: serif} | |
| 56 pre.smalldisplay {font-family: inherit; font-size: smaller} | |
| 57 pre.smallexample {font-size: smaller} | |
| 58 pre.smallformat {font-family: inherit; font-size: smaller} | |
| 59 pre.smalllisp {font-size: smaller} | |
| 60 span.nolinebreak {white-space: nowrap} | |
| 61 span.roman {font-family: initial; font-weight: normal} | |
| 62 span.sansserif {font-family: sans-serif; font-weight: normal} | |
| 63 ul.no-bullet {list-style: none} | |
| 64 --> | |
| 65 </style> | |
| 66 | |
| 67 | |
| 68 </head> | |
| 69 | |
| 70 <body lang="en"> | |
| 71 <a name="Plan-execution-in-Fortran"></a> | |
| 72 <div class="header"> | |
| 73 <p> | |
| 74 Next: <a href="Allocating-aligned-memory-in-Fortran.html#Allocating-aligned-memory-in-Fortran" accesskey="n" rel="next">Allocating aligned memory in Fortran</a>, Previous: <a href="FFTW-Fortran-type-reference.html#FFTW-Fortran-type-reference" accesskey="p" rel="prev">FFTW Fortran type reference</a>, Up: <a href="Calling-FFTW-from-Modern-Fortran.html#Calling-FFTW-from-Modern-Fortran" accesskey="u" rel="up">Calling FFTW from Modern Fortran</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p> | |
| 75 </div> | |
| 76 <hr> | |
| 77 <a name="Plan-execution-in-Fortran-1"></a> | |
| 78 <h3 class="section">7.4 Plan execution in Fortran</h3> | |
| 79 | |
| 80 <p>In C, in order to use a plan, one normally calls <code>fftw_execute</code>, | |
| 81 which executes the plan to perform the transform on the input/output | |
| 82 arrays passed when the plan was created (see <a href="Using-Plans.html#Using-Plans">Using Plans</a>). The | |
| 83 corresponding subroutine call in modern Fortran is: | |
| 84 </p><div class="example"> | |
| 85 <pre class="example"> call fftw_execute(plan) | |
| 86 </pre></div> | |
| 87 <a name="index-fftw_005fexecute-6"></a> | |
| 88 | |
| 89 <p>However, we have had reports that this causes problems with some | |
| 90 recent optimizing Fortran compilers. The problem is, because the | |
| 91 input/output arrays are not passed as explicit arguments to | |
| 92 <code>fftw_execute</code>, the semantics of Fortran (unlike C) allow the | |
| 93 compiler to assume that the input/output arrays are not changed by | |
| 94 <code>fftw_execute</code>. As a consequence, certain compilers end up | |
| 95 repositioning the call to <code>fftw_execute</code>, assuming incorrectly | |
| 96 that it does nothing to the arrays. | |
| 97 </p> | |
| 98 <p>There are various workarounds to this, but the safest and simplest | |
| 99 thing is to not use <code>fftw_execute</code> in Fortran. Instead, use the | |
| 100 functions described in <a href="New_002darray-Execute-Functions.html#New_002darray-Execute-Functions">New-array Execute Functions</a>, which take | |
| 101 the input/output arrays as explicit arguments. For example, if the | |
| 102 plan is for a complex-data DFT and was created for the arrays | |
| 103 <code>in</code> and <code>out</code>, you would do: | |
| 104 </p><div class="example"> | |
| 105 <pre class="example"> call fftw_execute_dft(plan, in, out) | |
| 106 </pre></div> | |
| 107 <a name="index-fftw_005fexecute_005fdft-3"></a> | |
| 108 | |
| 109 <p>There are a few things to be careful of, however: | |
| 110 </p> | |
| 111 <ul> | |
| 112 <li> <a name="index-fftw_005fexecute_005fdft_005fr2c-2"></a> | |
| 113 <a name="index-fftw_005fexecute_005fdft_005fc2r-1"></a> | |
| 114 <a name="index-fftw_005fexecute_005fr2r-1"></a> | |
| 115 You must use the correct type of execute function, matching the way | |
| 116 the plan was created. Complex DFT plans should use | |
| 117 <code>fftw_execute_dft</code>, Real-input (r2c) DFT plans should use use | |
| 118 <code>fftw_execute_dft_r2c</code>, and real-output (c2r) DFT plans should | |
| 119 use <code>fftw_execute_dft_c2r</code>. The various r2r plans should use | |
| 120 <code>fftw_execute_r2r</code>. Fortunately, if you use the wrong one you | |
| 121 will get a compile-time type-mismatch error (unlike legacy Fortran). | |
| 122 | |
| 123 </li><li> You should normally pass the same input/output arrays that were used when | |
| 124 creating the plan. This is always safe. | |
| 125 | |
| 126 </li><li> <em>If</em> you pass <em>different</em> input/output arrays compared to | |
| 127 those used when creating the plan, you must abide by all the | |
| 128 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 | |
| 129 requirement that the new arrays have the same alignment as the | |
| 130 original arrays; the best (and possibly only) way to guarantee this | |
| 131 is to use the ‘<samp>fftw_alloc</samp>’ 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 | |
| 132 use the <code>FFTW_UNALIGNED</code> flag when creating the | |
| 133 plan, in which case the plan does not depend on the alignment, but | |
| 134 this may sacrifice substantial performance on architectures (like x86) | |
| 135 with SIMD instructions (see <a href="SIMD-alignment-and-fftw_005fmalloc.html#SIMD-alignment-and-fftw_005fmalloc">SIMD alignment and fftw_malloc</a>). | |
| 136 <a name="index-FFTW_005fUNALIGNED-2"></a> | |
| 137 | |
| 138 </li></ul> | |
| 139 | |
| 140 <hr> | |
| 141 <div class="header"> | |
| 142 <p> | |
| 143 Next: <a href="Allocating-aligned-memory-in-Fortran.html#Allocating-aligned-memory-in-Fortran" accesskey="n" rel="next">Allocating aligned memory in Fortran</a>, Previous: <a href="FFTW-Fortran-type-reference.html#FFTW-Fortran-type-reference" accesskey="p" rel="prev">FFTW Fortran type reference</a>, Up: <a href="Calling-FFTW-from-Modern-Fortran.html#Calling-FFTW-from-Modern-Fortran" accesskey="u" rel="up">Calling FFTW from Modern Fortran</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p> | |
| 144 </div> | |
| 145 | |
| 146 | |
| 147 | |
| 148 </body> | |
| 149 </html> |
