Release Notes¶
This section includes significant changes, new features, performance improvements, and various issues. Unless noted, listed issues should not impact functionality. When functionality is impacted, we offer a work-around to avoid the issue (if available).
1.1.0¶
The first release of cuFFTDx library with support for Hopper and Ada architectures.
New Features¶
Initial support for Orin architecture (SM87).
Initial support for Ada architecture (SM89).
Initial support for Hopper architecture (SM90).
Added cufftdx::is_supported.
Added preliminary support for MSVC.
Improvements to the documentation:
Examples chapter,
Quick Installation Guide chapter,
information about shared memory usage in cuFFTDx, and
updated introduction chapter: First FFT Using cuFFTDx and Your Next Custom FFT Kernels.
Known Issues¶
Compiling using MSVC as CUDA host compiler requires enabling
__cplusplus(/Zc:__cplusplus). In order to do so, pass-Xcompiler "/Zc:__cplusplus"as an option to NVCC (NVCC: Options for Passing Specific Phase Options).When compiling using MSVC as CUDA host compiler please be aware of the limit on the length of mangled names and other compiler limits which in extreme cases can result in calling incorrect instances of kernel templates involving cuFFTDx.
1.0.0¶
The first general availability (GA) release of cuFFTDx library.
New Features¶
Added new shared API for block FFT execution, see block execution methods.
Added and documented FFT::stride.
Optimized default ElementsPerThread and FFTsPerBlock values for SM80 (targeting A100) and SM70 (targeting V100).
Restored full performance of powers-of-two kernels in cuFFTDx.
Resolved Issues¶
ptxaswarningprogram uses 32-bit address on line XXX which is conflicting with .address_size 64shouldn’t appear anymore.
0.3.1¶
The last early access (EA) release of cuFFTDx library.
Known Issues¶
ptxaswarning about pointer size conflict:ptxas warning : Program uses 32-bit address on line 'XXX' which is conflicting with .address_size 64
This warning may appear when compiling, but it does not impact functionality or performance.