After the above-mentioned improvements, Visual Studio 2022 17.8.2 generates: |test_ge2gt| PROC There is an extra MOV instruction to materialize the immediate into the register because it does not fit into encoding verbatim. So, the code-generation is the following by Visual Studio 2022 17.7: |test_ge2gt| PROC However, if we subtract it by 1 and turn greater equal (ge) into greater (gt) accordingly, then 0x10000 will fit into the shifted encoding.įor test_lt2le, the negative immediate, -0x1fff, does not fit into immediate encoding for ARM64 CMN instruction, but if we subtract it by 1 and turn less (lt) into less equal (le) accordingly, then -0x2000 will fit into shifted encoding.

Fromįor example: void test (double * _restrict a, unsigned long long * _restrict b)Ġx10001 inside test_ge2gt does not fit into the immediate encoding for the ARM64 CMP instruction, either verbatim or shifted.

Now, they are all enabled in the ARM64 backend and hooked up with the auto-vectorizer. The following conversions between floating-point and integer types are common in real-world code. Auto-Vec torizer supports conversions between floating-point and integer Also, we have optimized instruction selection for a few scalar code-generation scenarios, for example short circuit evaluation, comparison against immediate, and smarter immediate split for logic instruction. In the last couple of months, we have been improving code-generation for the auto-vectorizer so that it can generate Neon instructions for more cases. While there is already a blog “ Visual Studio 17.8 now available!” covering new features and improvements, we would like to share more information with you about what is new for the MSVC ARM64 backend in this blog. Visual Studio 2022 17.8 has been released recently (download it here).

Ms visual studio code