Files
rust/compiler/rustc_target/src/spec/arm_unknown_linux_musleabihf.rs

31 lines
1.2 KiB
Rust
Raw Normal View History

2019-02-08 21:00:07 +09:00
use crate::spec::{LinkerFlavor, Target, TargetOptions, TargetResult};
2016-04-27 18:02:31 -07:00
2016-07-30 15:44:59 -05:00
pub fn target() -> TargetResult {
let mut base = super::linux_musl_base::opts();
2016-04-27 18:02:31 -07:00
// Most of these settings are copied from the arm_unknown_linux_gnueabihf
// target.
2019-07-23 20:30:57 +02:00
base.features = "+strict-align,+v6,+vfp2,-d32".to_string();
base.max_atomic_width = Some(64);
2016-07-30 15:44:59 -05:00
Ok(Target {
2016-04-27 18:02:31 -07:00
// It's important we use "gnueabihf" and not "musleabihf" here. LLVM
// uses it to determine the calling convention and float ABI, and it
// doesn't support the "musleabihf" value.
llvm_target: "arm-unknown-linux-gnueabihf".to_string(),
target_endian: "little".to_string(),
target_pointer_width: "32".to_string(),
target_c_int_width: "32".to_string(),
data_layout: "e-m:e-p:32:32-Fi8-i64:64-v128:64:128-a:0:32-n32-S64".to_string(),
2016-04-27 18:02:31 -07:00
arch: "arm".to_string(),
target_os: "linux".to_string(),
target_env: "musl".to_string(),
2016-04-27 18:02:31 -07:00
target_vendor: "unknown".to_string(),
-Z linker-flavor This patch adds a `-Z linker-flavor` flag to rustc which can be used to invoke the linker using a different interface. For example, by default rustc assumes that all the Linux targets will be linked using GCC. This makes it impossible to use LLD as a linker using just `-C linker=ld.lld` because that will invoke LLD with invalid command line arguments. (e.g. rustc will pass -Wl,--gc-sections to LLD but LLD doesn't understand that; --gc-sections would be the right argument) With this patch one can pass `-Z linker-flavor=ld` to rustc to invoke the linker using a LD-like interface. This way, `rustc -C linker=ld.lld -Z linker-flavor=ld` will invoke LLD with the right arguments. `-Z linker-flavor` accepts 4 different arguments: `em` (emcc), `ld`, `gcc`, `msvc` (link.exe). `em`, `gnu` and `msvc` cover all the existing linker interfaces. `ld` is a new flavor for interfacing GNU's ld and LLD. This patch also changes target specifications. `linker-flavor` is now a mandatory field that specifies the *default* linker flavor that the target will use. This change also makes the linker interface *explicit*; before, it used to be derived from other fields like linker-is-gnu, is-like-msvc, is-like-emscripten, etc. Another change to target specifications is that the fields `pre-link-args`, `post-link-args` and `late-link-args` now expect a map from flavor to linker arguments. ``` diff - "pre-link-args": ["-Wl,--as-needed", "-Wl,-z,-noexecstack"], + "pre-link-args": { + "gcc": ["-Wl,--as-needed", "-Wl,-z,-noexecstack"], + "ld": ["--as-needed", "-z,-noexecstack"], + }, ``` [breaking-change] for users of custom targets specifications
2017-02-21 14:47:15 -05:00
linker_flavor: LinkerFlavor::Gcc,
2016-10-24 11:04:04 +02:00
options: TargetOptions {
unsupported_abis: super::arm_base::unsupported_abis(),
2019-03-31 23:17:49 +09:00
target_mcount: "\u{1}mcount".to_string(),
2019-12-22 17:42:04 -05:00
..base
2016-10-24 11:04:04 +02:00
},
2016-07-30 15:44:59 -05:00
})
2016-04-27 18:02:31 -07:00
}