Task #2697
improve FFT library flavor/version reporting
Description
With more FFT libraries supported, in particular clFFT but also ARMPL, version reporting could use some improvements.
At the moment, clFFT version is not reported anywhere; while cuFFT version can be inferred from the CUDA compiler version, it would be better to report it clearly and possibly unify it with the CPU fft library reporting.
TODO: check if ARMPL version is reported (AFAIK the name string is correctly reported with the fftw compat layer).
Related issues
History
#1 Updated by Szilárd Páll over 1 year ago
- Related to Task #2500: detect and allow linking external clFFT, or no clFFT added
#2 Updated by Erik Lindahl about 1 year ago
Just a note related to the CPU/library versioning: An important reason for writing all those things to the top of the header is to both make it easy to find and make sure we write this info right away in the execution (before we start doing anything advanced) in case mdrun crashes. In case we want information about clFFT, I think that will have to come much later.
#3 Updated by Mark Abraham about 1 year ago
Erik Lindahl wrote:
Just a note related to the CPU/library versioning: An important reason for writing all those things to the top of the header is to both make it easy to find and make sure we write this info right away in the execution (before we start doing anything advanced) in case mdrun crashes. In case we want information about clFFT, I think that will have to come much later.
Which version of clfft is configured is available, however. We just haven't written the code to report it.
#4 Updated by Szilárd Páll about 1 year ago
- Target version changed from 2019 to 2020
#5 Updated by Paul Bauer about 1 month ago
- Target version changed from 2020 to future