diff options
| author | Josh Triplett <josh@joshtriplett.org> | 2021-09-19 12:05:58 -0700 |
|---|---|---|
| committer | Mike Leany <55358344+mikeleany@users.noreply.github.com> | 2021-10-13 08:14:09 -0600 |
| commit | a23ee64c2c292f30fa64b258042e256bca0f35a9 (patch) | |
| tree | 03430927bf276a6aad3eff1ddbaddeec46d2f3ec /compiler/rustc_mir_transform/src/coverage/debug.rs | |
| parent | 5ba3a651f982fd716f5993b56961d2c3a535b7d8 (diff) | |
| download | rust-a23ee64c2c292f30fa64b258042e256bca0f35a9.tar.gz rust-a23ee64c2c292f30fa64b258042e256bca0f35a9.zip | |
Rename x86_64-unknown-none-elf to x86_64-unknown-none
Most Rust freestanding/bare-metal targets use just `-unknown-none` here, including aarch64-unknown-none, mipsel-unknown-none, and the BPF targets. The *only* target using `-unknown-none-elf` is RISC-V. The underlying toolchain doesn't care; LLVM accepts both `x86_64-unknown-none` and `x86_64-unknown-none-elf`. In addition, there's a long history of embedded x86 targets with varying definitions for the `elf` suffix; on some of those embedded targets, `elf` implied the inclusion of a C library based on newlib or similar. Using `x86_64-unknown-none` avoids any potential ambiguity there. (Work on this target sponsored by Profian.)
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions