I encountered what appears to be a bug in Intel IPP related to ippsFIRSR_Init32fc on Linux (IPP 2022.0).
I observed incorrect behavior in ippsFIRSR_32fc, which led me to investigate the initialization stage. During this investigation, I found that ippsFIRSR_Init32fc produces incorrect values in the pSpec structure when the pSpec and pTaps pointers refer to non-aligned memory.
When pSpec and pTaps are allocated using ippsMalloc, ippsFIRSR_Init32fc initializes pSpec correctly and ippsFIRSR_32fc works as expected.
However, when pSpec and pTaps point to statically allocated memory (i.e., memory that is not guaranteed to be aligned), the contents of pSpec differ from those produced when using ippsMalloc, and as a result ippsFIRSR_32fc behaves incorrectly.
This indicates that ippsFIRSR_Init32fc behaves differently depending on whether the provided memory is aligned or not. I could not find any documentation stating that pSpec and pTaps must be aligned when passed to ippsFIRSR_Init32fc. Based on this, it appears that either:
- the function has an undocumented alignment requirement, or
- this is a defect in ippsFIRSR_Init32fc.
