diff options
| author | WANG Xuerui <xen0n@gentoo.org> | 2024-02-05 13:18:32 +0800 |
|---|---|---|
| committer | WANG Xuerui <xen0n@gentoo.org> | 2024-02-05 13:38:50 +0800 |
| commit | 35dad14dfb63d77cf4a2077f1e8e9cff5a02a92b (patch) | |
| tree | 2f40cd66ce0fa9d387c651a3e269868f0a885bf0 /compiler/rustc_pattern_analysis/src | |
| parent | 991a9dc3f7f9aa4f56bbb7431e294ca52a34acfc (diff) | |
| download | rust-35dad14dfb63d77cf4a2077f1e8e9cff5a02a92b.tar.gz rust-35dad14dfb63d77cf4a2077f1e8e9cff5a02a92b.zip | |
target: default to the medium code model on LoongArch targets
The Rust LoongArch targets have been using the default LLVM code model so far, which is "small" in LLVM-speak and "normal" in LoongArch-speak. As described in the "Code Model" section of LoongArch ELF psABI spec v20231219 [1], one can only make function calls as far as ±128MiB with the "normal" code model; this is insufficient for very large software containing Rust components that needs to be linked into the big text section, such as Chromium. Because: * we do not want to ask users to recompile std if they are to build such software, * objects compiled with larger code models can be linked with those with smaller code models without problems, and * the "medium" code model is comparable to the "small"/"normal" one performance-wise (same data access pattern; each function call becomes 2-insn long and indirect, but this may be relaxed back into the direct 1-insn form in a future LLVM version), but is able to perform function calls within ±128GiB, it is better to just switch the targets to the "medium" code model, which is also "medium" in LLVM-speak. [1]: https://github.com/loongson/la-abi-specs/blob/v2.30/laelf.adoc#code-models
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions
