You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
As I understand right, mlas has explicit AVX512 instructions calls inside assembler code.
For the gcc compilation it is clear, corresponding source has corresponding compilation flags.
Could you, please, explain the logic in cmake file for the Windows build?
Why the arch:/AVX512 flag is not used for the corresponding sources?
If architecture is selected as MLAS_TARGET_AMD64, does it means that AVX512 instructions would forced to be used?
The *Avx512.asm files contains AVX512 instructions, and code is not enclosed by any #ifdef __AVX512F__.
Does it means that even if the CPU does not have such instructions, they would be in the execution file?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
As I understand right, mlas has explicit AVX512 instructions calls inside assembler code.
For the gcc compilation it is clear, corresponding source has corresponding compilation flags.
Could you, please, explain the logic in cmake file for the Windows build?
Why the arch:/AVX512 flag is not used for the corresponding sources?
If architecture is selected as MLAS_TARGET_AMD64, does it means that AVX512 instructions would forced to be used?
The
*Avx512.asm
files contains AVX512 instructions, and code is not enclosed by any#ifdef __AVX512F__
.Does it means that even if the CPU does not have such instructions, they would be in the execution file?
Beta Was this translation helpful? Give feedback.
All reactions