|
| 1 | +--- |
| 2 | +tier: "2" |
| 3 | +maintainers: |
| 4 | + - "[WANG Rui](https://github.com/heiher) `[email protected]`" |
| 5 | + - "[ZHAI Xiang](https://github.com/xiangzhai) `[email protected]`" |
| 6 | + - "[ZHAI Xiaojuan](https://github.com/zhaixiaojuan) `[email protected]`" |
| 7 | + - "[WANG Xuerui](https://github.com/xen0n) `[email protected]`" |
| 8 | +metadata: |
| 9 | + - target: "loongarch64-unknown-linux-gnu" |
| 10 | + notes: "LoongArch64 Linux, LP64D ABI (kernel 5.19, glibc 2.36)" |
| 11 | + std: true |
| 12 | + host: true |
| 13 | +--- |
| 14 | + |
| 15 | +## Overview |
| 16 | + |
| 17 | +[LoongArch] is a new RISC ISA developed by Loongson Technology Corporation Limited. |
| 18 | + |
| 19 | +[LoongArch]: https://loongson.github.io/LoongArch-Documentation/README-EN.html |
| 20 | + |
| 21 | +The target name follow this format: `<machine>-<vendor>-<os><fabi_suffix>`, where `<machine>` specifies the CPU family/model, `<vendor>` specifies the vendor and `<os>` the operating system name. |
| 22 | +While the integer base ABI is implied by the machine field, the floating point base ABI type is encoded into the os field of the specifier using the string suffix `<fabi-suffix>`. |
| 23 | + |
| 24 | +| `<fabi-suffix>` | `Description` | |
| 25 | +|------------------------|--------------------------------------------------------------------| |
| 26 | +| f64 | The base ABI use 64-bits FPRs for parameter passing. (lp64d)| |
| 27 | +| f32 | The base ABI uses 32-bit FPRs for parameter passing. (lp64f)| |
| 28 | +| sf | The base ABI uses no FPR for parameter passing. (lp64s) | |
| 29 | + |
| 30 | +<br> |
| 31 | + |
| 32 | +|`ABI type(Base ABI/ABI extension)`| `C library` | `kernel` | `target tuple` | |
| 33 | +|----------------------------------|-------------|----------|----------------------------------| |
| 34 | +| lp64d/base | glibc | linux | loongarch64-unknown-linux-gnu | |
| 35 | +| lp64f/base | glibc | linux | loongarch64-unknown-linux-gnuf32 | |
| 36 | +| lp64s/base | glibc | linux | loongarch64-unknown-linux-gnusf | |
| 37 | +| lp64d/base | musl libc | linux | loongarch64-unknown-linux-musl| |
| 38 | +| lp64f/base | musl libc | linux | loongarch64-unknown-linux-muslf32| |
| 39 | +| lp64s/base | musl libc | linux | loongarch64-unknown-linux-muslsf | |
| 40 | + |
| 41 | +## Requirements |
| 42 | + |
| 43 | +This target is cross-compiled. |
| 44 | +A GNU toolchain for LoongArch target is required. It can be downloaded from https://github.com/loongson/build-tools/releases, or built from the source code of GCC (12.1.0 or later) and Binutils (2.40 or later). |
| 45 | + |
| 46 | +## Building the target |
| 47 | + |
| 48 | +The target can be built by enabling it for a `rustc` build. |
| 49 | + |
| 50 | +```toml |
| 51 | +[build] |
| 52 | +target = ["loongarch64-unknown-linux-gnu"] |
| 53 | +``` |
| 54 | + |
| 55 | +Make sure `loongarch64-unknown-linux-gnu-gcc` can be searched from the directories specified in`$PATH`. Alternatively, you can use GNU LoongArch Toolchain by adding the following to `config.toml`: |
| 56 | + |
| 57 | +```toml |
| 58 | +[target.loongarch64-unknown-linux-gnu] |
| 59 | +# ADJUST THIS PATH TO POINT AT YOUR TOOLCHAIN |
| 60 | +cc = "/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc" |
| 61 | +cxx = "/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-g++" |
| 62 | +ar = "/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-ar" |
| 63 | +ranlib = "/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-ranlib" |
| 64 | +linker = "/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc" |
| 65 | +``` |
| 66 | + |
| 67 | +## Cross compilation |
| 68 | + |
| 69 | +This target can be cross-compiled on a `x86_64-unknown-linux-gnu` host. Cross-compilation on other hosts may work but is not tested. |
| 70 | + |
| 71 | +## Testing |
| 72 | +To test a cross-compiled binary on your build system, install the qemu binary that supports the LoongArch architecture and execute the following commands. |
| 73 | +```text |
| 74 | +CC_loongarch64_unknown_linux_gnu=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc \ |
| 75 | +CXX_loongarch64_unknown_linux_gnu=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-g++ \ |
| 76 | +AR_loongarch64_unknown_linux_gnu=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc-ar \ |
| 77 | +CARGO_TARGET_LOONGARCH64_UNKNOWN_LINUX_GNUN_LINKER=/TOOLCHAIN_PATH/bin/loongarch64-unknown-linux-gnu-gcc \ |
| 78 | +# SET TARGET SYSTEM LIBRARY PATH |
| 79 | +CARGO_TARGET_LOONGARCH64_UNKNOWN_LINUX_GNUN_RUNNER="qemu-loongarch64 -L /TOOLCHAIN_PATH/TARGET_LIBRARY_PATH" \ |
| 80 | +cargo run --target loongarch64-unknown-linux-gnu --release |
| 81 | +``` |
| 82 | +Tested on x86 architecture, other architectures not tested. |
| 83 | + |
| 84 | +## Building Rust programs |
| 85 | + |
| 86 | +Rust does not yet ship pre-compiled artifacts for this target. To compile for this target, you will either need to build Rust with the target enabled (see "Building the target" above), or build your own copy of `std` by using `build-std` or similar. |
| 87 | + |
| 88 | +If `rustc` has support for that target and the library artifacts are available, then Rust static libraries can be built for that target: |
| 89 | + |
| 90 | +```shell |
| 91 | +$ rustc --target loongarch64-unknown-linux-gnu your-code.rs --crate-type staticlib |
| 92 | +$ ls libyour_code.a |
| 93 | +``` |
| 94 | + |
| 95 | +On Rust Nightly it's possible to build without the target artifacts available: |
| 96 | + |
| 97 | +```text |
| 98 | +cargo build -Z build-std --target loongarch64-unknown-linux-gnu |
| 99 | +``` |
0 commit comments