Chris@19:
Chris@19: This bug was fixed in FFTW 1.2. There was a bug in
Chris@19: rfftwnd causing an incorrect amount of memory to be allocated. The bug showed
Chris@19: up in Linux with libc-5.3.12 (and nowhere else that we know of).
Chris@19:
Chris@19:
Chris@19:
Chris@19: These bugs were corrected in FFTW 1.2.1. The MPI transforms (really,
Chris@19: just the transpose routines) in FFTW 1.2 had bugs that could cause
Chris@19: errors in some situations.
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 1.3. (Older versions of FFTW did
Chris@19: work in single precision, but the test programs didn't--the error
Chris@19: tolerances in the tests were set for double precision.)
Chris@19:
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 1.3. FFTW 1.2.1 produced the right answer,
Chris@19: but the test program was wrong. For large n, n*n in the naive
Chris@19: transform that we used for comparison overflows 32 bit integer
Chris@19: precision, breaking the test.
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 2.0.1. (There was a 32-bit integer
Chris@19: overflow due to a poorly-parenthesized expression.)
Chris@19:
Chris@19:
Chris@19: There was a bug in the complex transforms that could cause incorrect
Chris@19: results under (hopefully rare) circumstances for lengths with
Chris@19: intermediate-size prime factors (17-97). This bug was fixed in FFTW
Chris@19: 2.1.1.
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 2.1.2. The 2.1/2.1.1 MPI test programs
Chris@19: crashed when using the MPICH implementation of MPI with the
Chris@19: ch_p4 device (TCP/IP); the transforms themselves worked fine.
Chris@19:
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 2.1.3. The multi-threaded transforms in
Chris@19: previous versions didn't work with AIX's
Chris@19: pthreads implementation, which idiosyncratically creates threads in detached
Chris@19: (non-joinable) mode by default.
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 2.1.3. FFTW's complex-transform algorithm
Chris@19: for prime sizes (in versions 2.0 to 2.1.2) had an integer overflow
Chris@19: problem that caused incorrect results for many primes greater than
Chris@19: 32768 (on 32-bit machines). (Sizes without large prime factors are
Chris@19: not affected.)
Chris@19:
Chris@19:
Chris@19: This bug was fixed in FFTW 2.1.4. (By default, Solaris creates
Chris@19: threads that do not parallelize over multiple processors, so one has
Chris@19: to request the proper behavior specifically.)
Chris@19:
Chris@19:
Chris@19:
Chris@19: The FFTW 2.1.3 configure script picked incorrect compiler flags for the xlc compiler on newer IBM processors. This
Chris@19: is fixed in FFTW 2.1.4.
Chris@19: Back: Internals of FFTW.
Chris@19: Return to contents.