Custom DLL - CPU specialization / performance

[Jörn]

Dear support,

if I use "normal" MKL, some DLLs are loaded at runtime, depending on the CPU / instruction set - for instance, "mkl_avx2.2.dll" or "mkl_avx512.2.dll".

But what happens if I build a custom DLL? Will the makefile magically include all versions for all instruction sets (for each exported function), or will I fall back to some lowest common denominator?

In other words: Will the performance of a custom DLL match the performance of "normal" MKL?

Thanks,

Jörn