annotate fft/fftw/fftw-3.3.4/doc/html/Memory-Allocation.html @ 40:223f770b5341 kissfft-double tip

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>Memory Allocation - 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="Data-Types-and-Files.html#Data-Types-and-Files" title="Data Types and Files">
Chris@19 9 <link rel="prev" href="Precision.html#Precision" title="Precision">
Chris@19 10 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
Chris@19 11 <!--
Chris@19 12 This manual is for FFTW
Chris@19 13 (version 3.3.4, 20 September 2013).
Chris@19 14
Chris@19 15 Copyright (C) 2003 Matteo Frigo.
Chris@19 16
Chris@19 17 Copyright (C) 2003 Massachusetts Institute of Technology.
Chris@19 18
Chris@19 19 Permission is granted to make and distribute verbatim copies of
Chris@19 20 this manual provided the copyright notice and this permission
Chris@19 21 notice are preserved on all copies.
Chris@19 22
Chris@19 23 Permission is granted to copy and distribute modified versions of
Chris@19 24 this manual under the conditions for verbatim copying, provided
Chris@19 25 that the entire resulting derived work is distributed under the
Chris@19 26 terms of a permission notice identical to this one.
Chris@19 27
Chris@19 28 Permission is granted to copy and distribute translations of this
Chris@19 29 manual into another language, under the above conditions for
Chris@19 30 modified versions, except that this permission notice may be
Chris@19 31 stated in a translation approved by the Free Software Foundation.
Chris@19 32 -->
Chris@19 33 <meta http-equiv="Content-Style-Type" content="text/css">
Chris@19 34 <style type="text/css"><!--
Chris@19 35 pre.display { font-family:inherit }
Chris@19 36 pre.format { font-family:inherit }
Chris@19 37 pre.smalldisplay { font-family:inherit; font-size:smaller }
Chris@19 38 pre.smallformat { font-family:inherit; font-size:smaller }
Chris@19 39 pre.smallexample { font-size:smaller }
Chris@19 40 pre.smalllisp { font-size:smaller }
Chris@19 41 span.sc { font-variant:small-caps }
Chris@19 42 span.roman { font-family:serif; font-weight:normal; }
Chris@19 43 span.sansserif { font-family:sans-serif; font-weight:normal; }
Chris@19 44 --></style>
Chris@19 45 </head>
Chris@19 46 <body>
Chris@19 47 <div class="node">
Chris@19 48 <a name="Memory-Allocation"></a>
Chris@19 49 <p>
Chris@19 50 Previous:&nbsp;<a rel="previous" accesskey="p" href="Precision.html#Precision">Precision</a>,
Chris@19 51 Up:&nbsp;<a rel="up" accesskey="u" href="Data-Types-and-Files.html#Data-Types-and-Files">Data Types and Files</a>
Chris@19 52 <hr>
Chris@19 53 </div>
Chris@19 54
Chris@19 55 <h4 class="subsection">4.1.3 Memory Allocation</h4>
Chris@19 56
Chris@19 57 <pre class="example"> void *fftw_malloc(size_t n);
Chris@19 58 void fftw_free(void *p);
Chris@19 59 </pre>
Chris@19 60 <p><a name="index-fftw_005fmalloc-145"></a><a name="index-fftw_005ffree-146"></a>
Chris@19 61 These are functions that behave identically to <code>malloc</code> and
Chris@19 62 <code>free</code>, except that they guarantee that the returned pointer obeys
Chris@19 63 any special alignment restrictions imposed by any algorithm in FFTW
Chris@19 64 (e.g. for SIMD acceleration). See <a href="SIMD-alignment-and-fftw_005fmalloc.html#SIMD-alignment-and-fftw_005fmalloc">SIMD alignment and fftw_malloc</a>.
Chris@19 65 <a name="index-alignment-147"></a>
Chris@19 66
Chris@19 67 <p>Data allocated by <code>fftw_malloc</code> <em>must</em> be deallocated by
Chris@19 68 <code>fftw_free</code> and not by the ordinary <code>free</code>.
Chris@19 69
Chris@19 70 <p>These routines simply call through to your operating system's
Chris@19 71 <code>malloc</code> or, if necessary, its aligned equivalent
Chris@19 72 (e.g. <code>memalign</code>), so you normally need not worry about any
Chris@19 73 significant time or space overhead. You are <em>not required</em> to use
Chris@19 74 them to allocate your data, but we strongly recommend it.
Chris@19 75
Chris@19 76 <p>Note: in C++, just as with ordinary <code>malloc</code>, you must typecast
Chris@19 77 the output of <code>fftw_malloc</code> to whatever pointer type you are
Chris@19 78 allocating.
Chris@19 79 <a name="index-C_002b_002b-148"></a>
Chris@19 80
Chris@19 81 <p>We also provide the following two convenience functions to allocate
Chris@19 82 real and complex arrays with <code>n</code> elements, which are equivalent
Chris@19 83 to <code>(double *) fftw_malloc(sizeof(double) * n)</code> and
Chris@19 84 <code>(fftw_complex *) fftw_malloc(sizeof(fftw_complex) * n)</code>,
Chris@19 85 respectively:
Chris@19 86
Chris@19 87 <pre class="example"> double *fftw_alloc_real(size_t n);
Chris@19 88 fftw_complex *fftw_alloc_complex(size_t n);
Chris@19 89 </pre>
Chris@19 90 <p><a name="index-fftw_005falloc_005freal-149"></a><a name="index-fftw_005falloc_005fcomplex-150"></a>
Chris@19 91 The equivalent functions in other precisions allocate arrays of <code>n</code>
Chris@19 92 elements in that precision. e.g. <code>fftwf_alloc_real(n)</code> is
Chris@19 93 equivalent to <code>(float *) fftwf_malloc(sizeof(float) * n)</code>.
Chris@19 94 <a name="index-precision-151"></a>
Chris@19 95 <!-- -->
Chris@19 96
Chris@19 97 </body></html>
Chris@19 98