2019-02-08 13:00:07 +01:00
|
|
|
use crate::spec::{LinkerFlavor, Target, TargetResult};
|
2015-12-29 23:33:58 +01:00
|
|
|
|
2016-07-24 18:47:39 +02:00
|
|
|
pub fn target() -> TargetResult {
|
2016-05-01 23:41:28 +02:00
|
|
|
let mut base = super::linux_musl_base::opts();
|
2015-12-29 23:33:58 +01:00
|
|
|
base.cpu = "pentium4".to_string();
|
2016-10-04 06:45:40 +02:00
|
|
|
base.max_atomic_width = Some(64);
|
-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 20:47:15 +01:00
|
|
|
base.pre_link_args.get_mut(&LinkerFlavor::Gcc).unwrap().push("-m32".to_string());
|
|
|
|
base.pre_link_args.get_mut(&LinkerFlavor::Gcc).unwrap().push("-Wl,-melf_i386".to_string());
|
2017-06-21 21:08:18 +02:00
|
|
|
base.stack_probes = true;
|
2015-12-29 23:33:58 +01:00
|
|
|
|
2017-01-21 00:32:47 +01:00
|
|
|
// The unwinder used by i686-unknown-linux-musl, the LLVM libunwind
|
|
|
|
// implementation, apparently relies on frame pointers existing... somehow.
|
|
|
|
// It's not clear to me why nor where this dependency is introduced, but the
|
|
|
|
// test suite does not pass with frame pointers eliminated and it passes
|
|
|
|
// with frame pointers present.
|
|
|
|
//
|
|
|
|
// If you think that this is no longer necessary, then please feel free to
|
|
|
|
// ignore! If it still passes the test suite and the bots then sounds good
|
|
|
|
// to me.
|
|
|
|
//
|
|
|
|
// This may or may not be related to this bug:
|
|
|
|
// https://llvm.org/bugs/show_bug.cgi?id=30879
|
|
|
|
base.eliminate_frame_pointer = false;
|
|
|
|
|
2016-07-24 18:47:39 +02:00
|
|
|
Ok(Target {
|
2015-12-29 23:33:58 +01:00
|
|
|
llvm_target: "i686-unknown-linux-musl".to_string(),
|
|
|
|
target_endian: "little".to_string(),
|
|
|
|
target_pointer_width: "32".to_string(),
|
2017-09-30 13:47:49 +02:00
|
|
|
target_c_int_width: "32".to_string(),
|
2016-04-18 14:38:45 +02:00
|
|
|
data_layout: "e-m:e-p:32:32-f64:32:64-f80:32-n8:16:32-S128".to_string(),
|
2015-12-29 23:33:58 +01:00
|
|
|
arch: "x86".to_string(),
|
|
|
|
target_os: "linux".to_string(),
|
|
|
|
target_env: "musl".to_string(),
|
|
|
|
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 20:47:15 +01:00
|
|
|
linker_flavor: LinkerFlavor::Gcc,
|
2015-12-29 23:33:58 +01:00
|
|
|
options: base,
|
2016-07-24 18:47:39 +02:00
|
|
|
})
|
2015-12-29 23:33:58 +01:00
|
|
|
}
|