2022-03-27 23:08:17 +00:00
|
|
|
use super::{cvs, wasm_base};
|
2022-06-17 14:38:42 +00:00
|
|
|
use super::{LinkerFlavor, PanicStrategy, RelocModel, Target, TargetOptions};
|
2016-09-06 00:41:50 +00:00
|
|
|
|
2020-10-05 12:37:55 +00:00
|
|
|
pub fn target() -> Target {
|
2020-12-30 18:52:21 +00:00
|
|
|
let mut options = wasm_base::options();
|
2021-01-21 23:58:50 +00:00
|
|
|
|
|
|
|
// Rust really needs a way for users to specify exports and imports in
|
|
|
|
// the source code. --export-dynamic isn't the right tool for this job,
|
|
|
|
// however it does have the side effect of automatically exporting a lot
|
|
|
|
// of symbols, which approximates what people want when compiling for
|
|
|
|
// wasm32-unknown-unknown expect, so use it for now.
|
2022-06-17 14:38:42 +00:00
|
|
|
options.add_pre_link_args(LinkerFlavor::Gcc, &["--export-dynamic"]);
|
|
|
|
options.add_post_link_args(LinkerFlavor::Em, &["-sABORTING_MALLOC=0", "-Wl,--fatal-warnings"]);
|
-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 19:47:15 +00:00
|
|
|
|
2016-09-06 00:41:50 +00:00
|
|
|
let opts = TargetOptions {
|
2022-03-22 10:43:05 +00:00
|
|
|
os: "emscripten".into(),
|
2020-10-08 19:22:28 +00:00
|
|
|
linker_flavor: LinkerFlavor::Em,
|
2019-08-17 05:08:01 +00:00
|
|
|
// emcc emits two files - a .js file to instantiate the wasm and supply platform
|
|
|
|
// functionality, and a .wasm file.
|
2022-03-22 10:43:05 +00:00
|
|
|
exe_suffix: ".js".into(),
|
2019-08-17 05:08:01 +00:00
|
|
|
linker: None,
|
2022-06-15 21:49:48 +00:00
|
|
|
relocation_model: RelocModel::Pic,
|
2019-10-18 21:47:54 +00:00
|
|
|
panic_strategy: PanicStrategy::Unwind,
|
2022-06-23 00:43:10 +00:00
|
|
|
no_default_libraries: false,
|
2022-03-27 23:08:17 +00:00
|
|
|
families: cvs!["unix", "wasm"],
|
2021-01-21 23:58:50 +00:00
|
|
|
..options
|
2016-09-06 00:41:50 +00:00
|
|
|
};
|
2020-10-05 12:37:55 +00:00
|
|
|
Target {
|
2022-03-22 10:43:05 +00:00
|
|
|
llvm_target: "wasm32-unknown-emscripten".into(),
|
2020-10-14 16:08:12 +00:00
|
|
|
pointer_width: 32,
|
2022-03-22 10:43:05 +00:00
|
|
|
data_layout: "e-m:e-p:32:32-p10:8:8-p20:8:8-i64:64-f128:64-n32:64-S128-ni:1:10:20".into(),
|
|
|
|
arch: "wasm32".into(),
|
2016-09-06 00:41:50 +00:00
|
|
|
options: opts,
|
2020-10-05 12:37:55 +00:00
|
|
|
}
|
2016-09-06 00:41:50 +00:00
|
|
|
}
|