Mercurial > hg > sv-dependency-builds
comparison src/fftw-3.3.5/doc/html/Plan-execution-in-Fortran.html @ 42:2cd0e3b3e1fd
Current fftw source
author | Chris Cannam |
---|---|
date | Tue, 18 Oct 2016 13:40:26 +0100 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
41:481f5f8c5634 | 42:2cd0e3b3e1fd |
---|---|
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.5, 30 July 2016). | |
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 5.2, http://www.gnu.org/software/texinfo/ --> | |
24 <head> | |
25 <title>FFTW 3.3.5: Plan execution in Fortran</title> | |
26 | |
27 <meta name="description" content="FFTW 3.3.5: Plan execution in Fortran"> | |
28 <meta name="keywords" content="FFTW 3.3.5: 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.smallquotation {font-size: smaller} | |
43 div.display {margin-left: 3.2em} | |
44 div.example {margin-left: 3.2em} | |
45 div.indentedblock {margin-left: 3.2em} | |
46 div.lisp {margin-left: 3.2em} | |
47 div.smalldisplay {margin-left: 3.2em} | |
48 div.smallexample {margin-left: 3.2em} | |
49 div.smallindentedblock {margin-left: 3.2em; font-size: smaller} | |
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.nocodebreak {white-space:nowrap} | |
61 span.nolinebreak {white-space:nowrap} | |
62 span.roman {font-family:serif; font-weight:normal} | |
63 span.sansserif {font-family:sans-serif; font-weight:normal} | |
64 ul.no-bullet {list-style: none} | |
65 --> | |
66 </style> | |
67 | |
68 | |
69 </head> | |
70 | |
71 <body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000"> | |
72 <a name="Plan-execution-in-Fortran"></a> | |
73 <div class="header"> | |
74 <p> | |
75 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> | |
76 </div> | |
77 <hr> | |
78 <a name="Plan-execution-in-Fortran-1"></a> | |
79 <h3 class="section">7.4 Plan execution in Fortran</h3> | |
80 | |
81 <p>In C, in order to use a plan, one normally calls <code>fftw_execute</code>, | |
82 which executes the plan to perform the transform on the input/output | |
83 arrays passed when the plan was created (see <a href="Using-Plans.html#Using-Plans">Using Plans</a>). The | |
84 corresponding subroutine call in modern Fortran is: | |
85 </p><div class="example"> | |
86 <pre class="example"> call fftw_execute(plan) | |
87 </pre></div> | |
88 <a name="index-fftw_005fexecute-6"></a> | |
89 | |
90 <p>However, we have had reports that this causes problems with some | |
91 recent optimizing Fortran compilers. The problem is, because the | |
92 input/output arrays are not passed as explicit arguments to | |
93 <code>fftw_execute</code>, the semantics of Fortran (unlike C) allow the | |
94 compiler to assume that the input/output arrays are not changed by | |
95 <code>fftw_execute</code>. As a consequence, certain compilers end up | |
96 repositioning the call to <code>fftw_execute</code>, assuming incorrectly | |
97 that it does nothing to the arrays. | |
98 </p> | |
99 <p>There are various workarounds to this, but the safest and simplest | |
100 thing is to not use <code>fftw_execute</code> in Fortran. Instead, use the | |
101 functions described in <a href="New_002darray-Execute-Functions.html#New_002darray-Execute-Functions">New-array Execute Functions</a>, which take | |
102 the input/output arrays as explicit arguments. For example, if the | |
103 plan is for a complex-data DFT and was created for the arrays | |
104 <code>in</code> and <code>out</code>, you would do: | |
105 </p><div class="example"> | |
106 <pre class="example"> call fftw_execute_dft(plan, in, out) | |
107 </pre></div> | |
108 <a name="index-fftw_005fexecute_005fdft-3"></a> | |
109 | |
110 <p>There are a few things to be careful of, however: | |
111 </p> | |
112 <ul> | |
113 <li> <a name="index-fftw_005fexecute_005fdft_005fr2c-2"></a> | |
114 <a name="index-fftw_005fexecute_005fdft_005fc2r-1"></a> | |
115 <a name="index-fftw_005fexecute_005fr2r-1"></a> | |
116 You must use the correct type of execute function, matching the way | |
117 the plan was created. Complex DFT plans should use | |
118 <code>fftw_execute_dft</code>, Real-input (r2c) DFT plans should use use | |
119 <code>fftw_execute_dft_r2c</code>, and real-output (c2r) DFT plans should | |
120 use <code>fftw_execute_dft_c2r</code>. The various r2r plans should use | |
121 <code>fftw_execute_r2r</code>. Fortunately, if you use the wrong one you | |
122 will get a compile-time type-mismatch error (unlike legacy Fortran). | |
123 | |
124 </li><li> You should normally pass the same input/output arrays that were used when | |
125 creating the plan. This is always safe. | |
126 | |
127 </li><li> <em>If</em> you pass <em>different</em> input/output arrays compared to | |
128 those used when creating the plan, you must abide by all the | |
129 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 | |
130 requirement that the new arrays have the same alignment as the | |
131 original arrays; the best (and possibly only) way to guarantee this | |
132 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 | |
133 use the <code>FFTW_UNALIGNED</code> flag when creating the | |
134 plan, in which case the plan does not depend on the alignment, but | |
135 this may sacrifice substantial performance on architectures (like x86) | |
136 with SIMD instructions (see <a href="SIMD-alignment-and-fftw_005fmalloc.html#SIMD-alignment-and-fftw_005fmalloc">SIMD alignment and fftw_malloc</a>). | |
137 <a name="index-FFTW_005fUNALIGNED-2"></a> | |
138 | |
139 </li></ul> | |
140 | |
141 <hr> | |
142 <div class="header"> | |
143 <p> | |
144 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> | |
145 </div> | |
146 | |
147 | |
148 | |
149 </body> | |
150 </html> |