Closed AtomicVar closed 9 months ago
Hello,
Thanks for being interested in VkFFT! Sorry for the long reply. I think it is hard to make the code being able to exclude some algorithms and it will be even harder to maintain, so I won't promise anything on this being ever implemented. I didn't think ~1MB was a big issue on most modern systems?
What I can suggest is using one of the way older versions of VkFFT which had fewer algorithms (like 1.2.17) and maybe this will suit your use case (though they didn't support metal).
Best regards, Dmitrii
The compiler will remove dead code if you tell it to. Your first example is ~10kb with clang++ -s -Os ...etc...
hope that helps
Hi! First, thank you for this awesome multi-platform GPU FFT library. I'm using it for an iOS App (Metal backend). The only thing that bothers me is that this library is header-only, which requires me to include all of its source code into my source code, and it makes the compiled binary have a large size.
Even for this most simple demo that include
vkFFT.h
and do nothing, the resulting executable is ~312KiB:After I added my code that only call some VkFFT APIs to do 2D FFT/iFFT, the executable comes to 1.2MiB:
My question: is it possible to "exclude" some stuffs that I don't need to make compiled binary have a smaller size? I can trade some performance for reducing binary size, e.g. be limited to use some simple algorithms, rather than trying all possible algorithms.