cannam@167: cannam@167: cannam@167: cannam@167: cannam@167:
cannam@167:cannam@167: Next: Acknowledgments, Previous: Upgrading from FFTW version 2, Up: Top [Contents][Index]
cannam@167:This chapter describes the installation and customization of FFTW, the cannam@167: latest version of which may be downloaded from cannam@167: the FFTW home page. cannam@167:
cannam@167:In principle, FFTW should work on any system with an ANSI C compiler
cannam@167: (gcc
is fine). However, planner time is drastically reduced if
cannam@167: FFTW can exploit a hardware cycle counter; FFTW comes with cycle-counter
cannam@167: support for all modern general-purpose CPUs, but you may need to add a
cannam@167: couple of lines of code if your compiler is not yet supported
cannam@167: (see Cycle Counters). (On Unix, there will be a warning at the end
cannam@167: of the configure
output if no cycle counter is found.)
cannam@167:
cannam@167:
cannam@167:
cannam@167:
Installation of FFTW is simplest if you have a Unix or a GNU system, cannam@167: such as GNU/Linux, and we describe this case in the first section below, cannam@167: including the use of special configuration options to e.g. install cannam@167: different precisions or exploit optimizations for particular cannam@167: architectures (e.g. SIMD). Compilation on non-Unix systems is a more cannam@167: manual process, but we outline the procedure in the second section. It cannam@167: is also likely that pre-compiled binaries will be available for popular cannam@167: systems. cannam@167:
cannam@167:Finally, we describe how you can customize FFTW for particular needs by cannam@167: generating codelets for fast transforms of sizes not supported cannam@167: efficiently by the standard FFTW distribution. cannam@167: cannam@167:
cannam@167:• Installation on Unix: | cannam@167: | |
• Installation on non-Unix systems: | cannam@167: | |
• Cycle Counters: | cannam@167: | |
• Generating your own code: | cannam@167: |
cannam@167: Next: Acknowledgments, Previous: Upgrading from FFTW version 2, Up: Top [Contents][Index]
cannam@167: