OSX/Linux error: use of undeclared identifier '_mm_loadu_si32'

[Mykola83]

Intel Intrinsic Guide states it's pretty old SSE2 instruction,

https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=_mm_loadu_si32&expand=3419

but why I can't find it on Linux/OSX ?

On OSX I searched through

/Library/Developer/CommandLineTools/usr/lib/tapi/10.0.0/include/emmintrin.h

but nothing found.

[AbhishekD_Intel]

Hi,

Thanks for reaching out to us.

It seems that you are not looking "_mm_loadu_si32" into the correct file.

Please try searching this in "immintrin.h" header file, you will definitely find it.

I have checked it in my environment and its there. Please find the below result for more details.

[]$ cat /opt/intel/compiler/2020u1/compilers_and_libraries_2020.1.217/linux/compiler/include/icc/immintrin.h | grep -i _mm_loadu_si32

extern __m128i __ICL_INTRINCC _mm_loadu_si32(void const*);

[]$ icc -v

icc version 19.1.1.217 (gcc version 4.8.5 compatibility)

Warm Regards,

Abhishek

[Mykola83]

Actually, I don't use Intel compiler.

I use gcc/clang.

[Viet_H_Intel]

These are Intel Intrinsic. You need to have Intel compiler installed in order to use them.

Thanks,

[Mykola83]

I have Intel compiler installed.

But what I found is that my problem really exists.

And it was fixed only last year in GCC 9 !!!

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78782

[AbhishekD_Intel · Accepted solution]

Hi,

Please update us if the provided details help you. As this is Intel Intrinsic we will recommend you to use Intel Compiler. We can only provide support to the Intel specific issues.

As this intrinsic is already present so can we close this thread?

If you have any issues related to this thread please update us. Also, feel free to post a new thread if have more Intel compiler-related issues.

Warm Regards,

Abhishek

[AbhishekD_Intel]

Hi,

Please give us an update related to this issue.

Thank You

[Mykola83]

Ok, lets close the issue, as not Intel issue.

[AbhishekD_Intel]

Thank you for the confirmation. We will no longer monitor this issue. Feel free to post a new thread if you have any issues.