diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-03-29 21:08:11 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-29 21:08:11 +0100 |
| commit | 2b0c2f7904ea460e471f6b0e0f7e2cf6f14e7186 (patch) | |
| tree | dccc65c1a50148566631c8ac547e667e39889cd8 /compiler/rustc_codegen_llvm/src | |
| parent | 7ef7034caf03916582053eb42be8a0422539687a (diff) | |
| parent | eab700a0aa4ad3079ad043a9cb4fb89edab3b4b7 (diff) | |
| download | rust-2b0c2f7904ea460e471f6b0e0f7e2cf6f14e7186.tar.gz rust-2b0c2f7904ea460e471f6b0e0f7e2cf6f14e7186.zip | |
Rollup merge of #138431 - madsmtm:uclibc-llvm-target, r=jieyouxu
Fix `uclibc` LLVM target triples `uclibc` is not an environment understood by LLVM, it is only a concept in Clang that can be selected with `-muclibc` (it affects which dynamic linker is passed to the static linker's `-dynamic-linker` flag). In fact, using `uclibcgnueabi`/`uclibc` is actively harmful, as it prevents LLVM from seeing that the target is gnu-like; we should use `gnueabi`/`gnu` directly instead. Motivation: To make it easier to verify that [`cc-rs`' conversion from `rustc` to Clang/LLVM triples](https://github.com/rust-lang/cc-rs/issues/1431) is correct. **There are no target maintainers for these targets.** So I'll CC ``@lancethepants`` and ``@skrap`` who maintain the related `armv7-unknown-linux-uclibceabi` and `armv7-unknown-linux-uclibceabihf` (both of which already pass `-gnu` instead of `-uclibc`) in case they have any insights. r? jieyouxu
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions
