Difference between revisions of "SVE2"

From CDOT Wiki
Jump to: navigation, search
(C Compiler Options)
(Running SVE2 Code)
Line 40: Line 40:
 
== Running SVE2 Code ==
 
== Running SVE2 Code ==
  
To run SVE2 code on an Armv8 system, you can use the QEMU usermode system. This will trap SVE2 instructions and emulate them in software, while executing Armv8a instructions directly on the hardware:
+
To run SVE2 code on an Armv8 computer, you can use the QEMU usermode software. This will trap SVE2 instructions and emulate them in software, while executing Armv8a instructions directly on the hardware:
  
 
  qemu-aarch64 ''./binary''
 
  qemu-aarch64 ''./binary''
  
 
{{Admon/tip|Running AArch64 code on x86_64|The QMEU user mode software can also be used to run AArch64 code on an x86_64 system (albeit slowly). However, this requires a full AArch64 userspace (applications and tools, such as ld) to be installed on the x86_64 system.}}
 
{{Admon/tip|Running AArch64 code on x86_64|The QMEU user mode software can also be used to run AArch64 code on an x86_64 system (albeit slowly). However, this requires a full AArch64 userspace (applications and tools, such as ld) to be installed on the x86_64 system.}}

Revision as of 12:07, 25 March 2022

The Armv9 Scalable Vector Extensions verision 2 (SVE2) provide a variable-witdh SIMD capability for AArch64 systems. Note that SVE2 is a minor refinement and standardization of the original Scalable Vector Extensions (used on the Fugaku supercomputer), so most materials discussing SVE are also applicable to SVE2 (which will be used on systems ranging from smartphones to servers to supercomputers).

Resources

Building SVE2 Code

C Compiler Options

At the time of writing (March 2022), most compilers do not have a specific target for Armv9 systems. Therefore, to build code that includes SVE2 instructions, you will need to instruct the complier to emit code for an Armv8-a processor that also understands the SVE2 instructions; on the GCC compiler, this is performed using the -march= option (which is read as "machine architecture"). You must do this regardless of whether you're using autovectorization, inline assembler, or intrinsics. The architecture specificaion for this target is currently "armv8-a+sve2":

gcc -march=armv8-a+sve2 ...

Remember that in order to invoke the autovectorizer in GCC version 11, you must use -O3 or the appropriate feature options (-ftree-vectorize):

gcc -O3 -march=armv8-a+sve2 ...

gcc -O2 -march=armv8-a+sve2 -ftree-vectorize ...

Using SVE2 Intrinsics Header Files

To use SVE2 intrinsics in a C program, include the header file arm_sve.h:

#include <arm_sve.h>

Note: some ARM documentation will refer to <arm_sve2.h>, but in gcc, the correct file is <arm_sve.h>

Macro for SVE2

To detect SVE2 capability in the compilation target, use the macro __ARM_FEATURE_SVE2:

#if __ARM_FEATURE_SVE2
...
#endif

Running SVE2 Code

To run SVE2 code on an Armv8 computer, you can use the QEMU usermode software. This will trap SVE2 instructions and emulate them in software, while executing Armv8a instructions directly on the hardware:

qemu-aarch64 ./binary
Idea.png
Running AArch64 code on x86_64
The QMEU user mode software can also be used to run AArch64 code on an x86_64 system (albeit slowly). However, this requires a full AArch64 userspace (applications and tools, such as ld) to be installed on the x86_64 system.