-
33e352cf
by Sven Tennie at 2025-07-27T12:42:55+02:00
Introduce -mriscv-vlen driver argument with runtime check
Ensure that the configured vlen fits to the detected one.
Docs version
-
c222800f
by Sven Tennie at 2025-07-27T12:42:55+02:00
Compile AutoApply_V*.cmm and Jumps_V*.cmm with vector support
If the running CPU does not support RVV, this code will not be executed.
However, at build time, we have to emit (prepare) it.
-
1109dbad
by Sven Tennie at 2025-07-27T12:42:55+02:00
RV64: Emit code for vector extension (RVV)
This includes adding the vector registers to the register allocator and
adding support for the related MachOps to the native code generator.
Also, fix FMA support while implementing vector FMA.
-
a2379744
by Sven Tennie at 2025-07-27T12:42:55+02:00
point free: floatVecFormat & intVecFormat
Drive-by refactoring.
-
86586e06
by Sven Tennie at 2025-07-27T12:42:55+02:00
RV64: Detect RVV CPU features and make them configurable for CROSS_EMULATOR
Unfortunately, the cpuinfo Python package is abandonned. Thus, we just
add RVV detection here (and not upstream.)
cpuinfo is not executed on the CROSS_EMULATOR. So, we make supported
features configurable.
Also, adjust the related testlib functions to cover RISC-V. And, use
them in tests.
-
2d39200f
by Sven Tennie at 2025-07-27T12:42:55+02:00
Test for the RVV (RISC-V vectors) C calling convention
This could be enhanced to cover other architectures as well.
-
2d46b39d
by Sven Tennie at 2025-07-27T12:42:55+02:00
RV64: Always configure -march=rv64gcv
Independent of if RVV is supported by the executing processor, we need
to be able to compile code for it.
-
addc1856
by Sven Tennie at 2025-07-27T12:42:55+02:00
RV64: Check for GCC >= 14 in autoconf
Older versions use another (obsolete) C calling convention. So, we must
limit ourselves here to newer GCCs.
-
522214d0
by Sven Tennie at 2025-07-27T12:42:55+02:00
RV64: Test and fix (V)FMA
Use the testlib predicate to reduce code duplications.