Which Intel FFT to use - IPP or MKL?

Useful Tools and Components
21

Thanks, I’ll see if that works here… the ipp folder is a shortcut and if you drag the ipp include path into the field in Xcode it’s expanded into the full path:

/opt/intel/compilers_and_libraries_2017.4.181/mac/ipp/include.

This seems like the same thing I’m doing for the MKL lib which isn’t working though.

Cheers,

Rail

22

@yairadix
Interesting small setup, will try that as well

23

I’ll give those a shot… doing the same thing for the MKL library didn’t work though… but I hadn’t included the compiler lib path… and since I was trying to use the MKL library I didn’t init it.

I’m using 10.11.6 on the dev iMac so am also using an older IPP version.

I did find a macro HAS_IPP in JUCE but it’s not defined and appears to be for Core Audio only.

Thanks,

Rail

1 Like
24

Now this was interesting…

If I added the libs to the Extra linker flags in PJ it worked… but if I followed the DSP instructions…

/** Config: JUCE_DSP_USE_INTEL_MKL

    If this flag is set, then JUCE will use Intel's MKL for JUCE's FFT and
    convolution classes.

    The folder containing the mkl_dfti.h header must be in your header
    search paths when using this flag. You also need to add all the necessary
    intel mkl libraries to the "External Libraries to Link" field in the
    Projucer.
*/
#ifndef JUCE_DSP_USE_INTEL_MKL
 #define JUCE_DSP_USE_INTEL_MKL 0
#endif

and added them in PJ to “External Libraries to Link” it failed. The latter prepends the libs in the project’s “Other Linker Flags” with -l whereas using PJ’s “Extra linker Flags” it doesn’t.

Thanks,

Rail

25

Hi,

Just following up to see if you’ll add IPP support?

Thanks,

Rail

4 Likes