Did GLM_FORCE_SIMD_AVX2 change to GLM_FORCE_AVX2? Because in the manual.pdf and the sources I've seen on the internet says:
#define GLM_FORCE_SIMD_AVX2
#include <glm/glm.hpp>
// If the compiler doesn’t support AVX2 instrinsics, compiler errors will happen.
But I did a complete search for GLM_FORCE_SIMD_AVX2 and the only place it comes up is in manual.pdf.
However I did find GLM_FORCE_AVX2 in one place, in a file called platform.h. It must have changed, right? Am I just supposed to define GLM_FORCE_AVX2 before I include any GLM headers? Because I still don't think this is activating it.
Did GLM_FORCE_SIMD_AVX2 change to GLM_FORCE_AVX2? Because in the manual.pdf and the sources I've seen on the internet says:
#define GLM_FORCE_SIMD_AVX2
#include <glm/glm.hpp>
// If the compiler doesn’t support AVX2 instrinsics, compiler errors will happen.
But I did a complete search for GLM_FORCE_SIMD_AVX2 and the only place it comes up is in manual.pdf.
However I did find GLM_FORCE_AVX2 in one place, in a file called platform.h. It must have changed, right? Am I just supposed to define GLM_FORCE_AVX2 before I include any GLM headers? Because I still don't think this is activating it.
Share Improve this question edited Feb 17 at 23:17 user2357112 281k31 gold badges479 silver badges561 bronze badges asked Feb 17 at 22:57 ZebrafishZebrafish 14k3 gold badges64 silver badges152 bronze badges1 Answer
Reset to default 1It doesn't look like GLM_FORCE_SIMD_AVX2
ever existed. The correct define seems to have always been GLM_FORCE_AVX2
.
The Git blame shows that that line of the manual was changed in a commit from 2018. According to the commit message, the commit was just supposed to reanize section 2 of the manual, but it ended up changing the section to talk about a general GLM_FORCE_SIMD_**
category of defines that didn't actually exist, even in the repository state at the time.
Since then, the erroneous GLM_FORCE_SIMD_**
reference was taken out in another commit, but the GLM_FORCE_SIMD_AVX2
code example still remains.