This repository is a fork of the LLVM project, with the addition of the T-Head Vector (XTHeadVector
) extension.
Currently, the work is still in progress.
We listed features that have been implemented or are being worked on in the following itemized table,
as of the date of this commit.
An item marked as (Done)
means that it has been fully implemented and tested according to the specification,
while the one marked as (WIP)
means that only part of it has been implemented and may not be fully tested.
Any feature not listed below but present in the specification should be considered as a (TODO)
.
- (Done) LLVM MC instruction definitions, assembly and disassembly.
- (WIP) LLVM intrinsics related to the
XTHeadVector
extension:- (WIP)
6. Configuration-Setting and Utility
- (Done)
6.1. Set vl and vtype
- (Done)
6.2. Set vl to VLMAX with specific vtype
- (Done)
6.6. Read/Write URW vector CSRs
- (Done)
- (WIP)
7. Vector Load/Store
- (Done)
7.1. Vector Unit-Stride Operations
- (Done)
7.2. Vector Strided Load/Store Operations
- (Done)
7.3. Vector Indexed Load/Store Operations
- (Done)
7.4. Unit-stride Fault-Only-First Loads Operations
- (Done)
7.5. Vector Load/Store Segment Operations (Zvlsseg)
, which is an essential part ofXTHeadVector
- (Done)
- (Done)
8. Vector AMO Operations (Zvamo)
, which isXTHeadZvamo
regarding theXTHeadVector
extension. - (WIP)
12. Vector Integer Arithmetic Operations
- (Done)
12.1. Vector Single-Width Integer Add and Subtract
- (Done)
vadd.{vv,vx,vi}
- (Done)
vsub.{vv,vx}
- (Done)
vrsub.{vx,vi}
- (Done)
- (Done)
12.2. Vector Widening Integer Add/Subtract
- (Done)
vwadd{u}.{vv,vx,wv,wx}
- (Done)
vwsub{u}.{vv,vx,wv,wx}
- (Done)
- (Done)
12.3. Vector Integer Add-with-Carry / Subtract-with-Borrow Instructions
- (Done)
vadc.{vvm,vxm,vim}
- (Done)
vmadc.{vvm,vxm,vim}
- (Done)
vsbc.{vvm,vxm}
- (Done)
vmsbc.{vvm,vxm}
- (Done)
- (Done)
12.4. Vector Bitwise Logical Instructions
- (Done)
vand.{vv,vx,vi}
- (Done)
vor.{vv,vx,vi}
- (Done)
vxor.{vv,vx,vi}
- (Done)
- (Done)
12.5. Vector Single-Width Bit Shift Instructions
- (Done)
vsll.{vv,vx,vi}
- (Done)
vsrl.{vv,vx,vi}
- (Done)
vsra.{vv,vx,vi}
- (Done)
- (Done)
12.6. Vector Narrowing Integer Right Shift Instructions
- (Done)
12.7 Vector Integer Comparison Instructions
- (Done)
12.8. Vector Integer Min/Max Instructions
- (Done)
12.9. Vector Single-Width Integer Multiply Instructions
- (Done)
12.10. Vector Integer Divide Instructions
- (Done)
12.11. Vector Widening Integer Multiply Instructions
- (Done)
12.12. Vector Single-Width Integer Multiply-Add Instructions
- (Done)
12.13. Vector Widening Integer Multiply-Add Instructions
- (Done)
12.14. Vector Integer Merge and Move Instructions
- (Done)
- (WIP)
13. Vector Fixed-Point Arithmetic Instructions
- (Done)
13.1. Vector Single-Width Saturating Add and Subtract
- (Done)
13.2. Vector Single-Width Averaging Add and Subtract
- (Done)
13.3. Vector Single-Width Fractional Multiply with Rounding and Saturation
- (Done)
13.6. Vector Narrowing Fixed-Point Clip Instructions
- (Done)
- (WIP)
14. Vector Floating-Point Instructions
- (Done)
14.2. Vector Single-Width Floating-Point Add/Subtract Instructions
- (Done)
14.3. Vector Widening Floating-Point Add/Subtract Instructions
- (Done)
14.4. Vector Single-Width Floating-Point Multiply/Divide Instructions
- (Done)
14.5. Vector Widening Floating-Point Multiply
- (Done)
- (WIP)
- (WIP) Clang intrinsics related to the
XTHeadVector
extension:- (WIP)
6. Configuration-Setting and Utility
- (Done)
6.1. Set vl and vtype
- (Done)
6.2. Set vl to VLMAX with specific vtype
- (Done)
- (WIP)
7. Vector Load/Store
- (Done)
7.1. Vector Unit-Stride Operations
- (Done)
7.2. Vector Strided Load/Store Operations
- (Done)
7.3. Vector Indexed Load/Store Operations
- (Done)
7.4 Unit-stride Fault-Only-First Loads Operations
- (WIP)
7.5. Vector Load/Store Segment Operations (Zvlsseg)
- (Done)
7.5.1. Vector Unit-Stride Segment Loads and Stores
- (Done)
- (Done)
- (WIP)
Build it as you are building the official LLVM project, but remember to enable the RISCV
target.
We provide a configuration used during development:
cmake -G Ninja \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DLLVM_ENABLE_PROJECTS="clang" \
-DLLVM_TARGETS_TO_BUILD="RISCV" \
-DBUILD_SHARED_LIBS=true \
-DLLVM_USE_LINKER=mold \
-DDEFAULT_SYSROOT="/opt/riscv/sysroot" \
-DLLVM_DEFAULT_TARGET_TRIPLE="riscv64-unknown-linux-gnu"
Where /opt/riscv/sysroot
is a directory containing the headers and libraries of the target system.
For details, please refer to the RISC-V GNU toolchain.
We also recommend mold as the linker, as it is unbelievably fast and memory-efficient.
This is an example of how to use the XTHeadVector
extension in C code:
// memcpy_v.c
#include <riscv_vector.h>
#include <stdint.h>
#include <stdio.h>
void memcpy_v(uint8_t *dst, const uint8_t *src, size_t n) {
for (size_t vl; n > 0; n -= vl, src += vl, dst += vl) {
vl = __riscv_vsetvl_e8m4(n);
vuint8m4_t vec_src = __riscv_th_vle8_v_u8m4(src, vl);
__riscv_th_vse8_v_u8m4(dst, vec_src, vl);
}
}
/* main() function omitted */
The code implements a vectorized version of memcpy()
. To compile it:
clang -march=rv64gc_xtheadvector memcpy_v.c -o memcpy_v
To inspect the LLVM IR generated, use the -S
option:
clang -march=rv64gc_xtheadvector memcpy_v.c -o memcpy_v.ll -S -emit-llvm
To compile the LLVM IR to an executable binary, use the llc
tool:
llc -mtriple=riscv64 -mattr=+xtheadvector memcpy_v.ll
You may encounter some errors about missing libraries when using sysroot from GCC, lik
/opt/riscv/bin/riscv64-unknown-linux-gnu-ld: cannot find crtbeginS.o: No such file or directory
/opt/riscv/bin/riscv64-unknown-linux-gnu-ld: cannot find -lgcc: No such file or directory
/opt/riscv/bin/riscv64-unknown-linux-gnu-ld: cannot find -lgcc: No such file or directory
Here's a workaround, where /opt/riscv
should be replaced with the path to your
RISC-V GNU toolchain mentioned above:
cd <path-to-the-build-directory>
ln -s /opt/riscv/lib/gcc lib/gcc
Sure! Please feel free to open an issue or a pull request for any questions or suggestions.
We prioritize work based on "easiest to see results" and "most frequently used" by the compiler, but any kind of contribution is always welcomed.
Yes! We are working on it. We will start to submit pull requests to the official LLVM project once one of the following conditions is met:
- The
XTHeadVector
extension is fully implemented and tested, and the code is clean and well-documented. Currently, the code in this repo is still far from "elegant." There are copy-pasted functions, duplicated code segments, or hard-coded values, which are not acceptable in the upstream project. We also have a plan about reusing the existing RVV 1.0 implementation in LLVM, but it takes time to figure out the correct way, as our priority is to make the compiler work first. - There are people in the GCC community who are also working on the same extension. We plan to reach out to the LLVM community once GCC has merged their first patch.
- The
XTHeadVector
extension is still supported and used by T-Head boards when any of the above conditions is met.
Here's the original README.md from the LLVM project:
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called "LLVM". This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.