Debug vs Release differences when using optzAdd2.for from IntelSP library

Intel® oneAPI Math Kernel Library

Ask questions and share information with other developers who use Intel® Math Kernel Library.

Debug vs Release differences when using optzAdd2.for from IntelSP library

548 Views

Dear forum,

I found differences between the calculations resulted from optzAdd2.for from Intel Signal Processing library.

If I turn on the global optimization, optimize for speed, or full optimization then the release version sometimes deviate quite significantly from the debug version. If I use local or no optimization, then the results of the debug and the release versions are the same.

I have checked that the inputs to the routine optzAdd2 are the same for both release and debug. There's no memory leak problem that I can detect, everything is initialized.

Is there a possibility that the routine optzAdd2 can only be optimized locally ?

Are there any users who have had similar experienes with the routines from signal processing library ?

Many thanks in advance,

Patricia Astrid

Link Copied

0 Replies

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.