-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rustc: Allow using clang
for wasm32 targets
#59320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,123 @@ | ||
use std::collections::BTreeMap; | ||
use super::{LldFlavor, TargetOptions, PanicStrategy, LinkerFlavor}; | ||
|
||
pub fn options() -> TargetOptions { | ||
let mut lld_args = Vec::new(); | ||
let mut clang_args = Vec::new(); | ||
let mut arg = |arg: &str| { | ||
lld_args.push(arg.to_string()); | ||
clang_args.push(format!("-Wl,{}", arg)); | ||
}; | ||
|
||
// There have been reports in the wild (rustwasm/wasm-bindgen#119) of | ||
// using threads causing weird hangs and bugs. Disable it entirely as | ||
// this isn't yet the bottleneck of compilation at all anyway. | ||
// | ||
// FIXME: we should file an upstream issue with LLD about this | ||
arg("--no-threads"); | ||
|
||
// By default LLD only gives us one page of stack (64k) which is a | ||
// little small. Default to a larger stack closer to other PC platforms | ||
// (1MB) and users can always inject their own link-args to override this. | ||
arg("-z"); | ||
arg("stack-size=1048576"); | ||
|
||
// By default LLD's memory layout is: | ||
// | ||
// 1. First, a blank page | ||
// 2. Next, all static data | ||
// 3. Finally, the main stack (which grows down) | ||
// | ||
// This has the unfortunate consequence that on stack overflows you | ||
// corrupt static data and can cause some exceedingly weird bugs. To | ||
// help detect this a little sooner we instead request that the stack is | ||
// placed before static data. | ||
// | ||
// This means that we'll generate slightly larger binaries as references | ||
// to static data will take more bytes in the ULEB128 encoding, but | ||
// stack overflow will be guaranteed to trap as it underflows instead of | ||
// corrupting static data. | ||
arg("--stack-first"); | ||
|
||
// FIXME we probably shouldn't pass this but instead pass an explicit | ||
// whitelist of symbols we'll allow to be undefined. We don't currently have | ||
// a mechanism of knowing, however, which symbols are intended to be | ||
// imported from the environment and which are intended to be imported from | ||
// other objects linked elsewhere. This is a coarse approximation but is | ||
// sure to hide some bugs and frustrate someone at some point, so we should | ||
// ideally work towards a world where we can explicitly list symbols that | ||
// are supposed to be imported and have all other symbols generate errors if | ||
// they remain undefined. | ||
arg("--allow-undefined"); | ||
|
||
// Rust code should never have warnings, and warnings are often | ||
// indicative of bugs, let's prevent them. | ||
arg("--fatal-warnings"); | ||
|
||
// LLD only implements C++-like demangling, which doesn't match our own | ||
// mangling scheme. Tell LLD to not demangle anything and leave it up to | ||
// us to demangle these symbols later. Currently rustc does not perform | ||
// further demangling, but tools like twiggy and wasm-bindgen are intended | ||
// to do so. | ||
arg("--no-demangle"); | ||
|
||
// The symbol visibility story is a bit in flux right now with LLD. | ||
// It's... not entirely clear to me what's going on, but this looks to | ||
// make everything work when `export_symbols` isn't otherwise called for | ||
// things like executables. | ||
// | ||
// This is really only here to get things working. If it can be removed and | ||
// basic tests still work, then sounds like it should be removed! | ||
arg("--export-dynamic"); | ||
|
||
let mut pre_link_args = BTreeMap::new(); | ||
pre_link_args.insert(LinkerFlavor::Lld(LldFlavor::Wasm), lld_args); | ||
pre_link_args.insert(LinkerFlavor::Gcc, clang_args); | ||
|
||
TargetOptions { | ||
// we allow dynamic linking, but only cdylibs. Basically we allow a | ||
// final library artifact that exports some symbols (a wasm module) but | ||
// we don't allow intermediate `dylib` crate types | ||
dynamic_linking: true, | ||
only_cdylib: true, | ||
|
||
// This means we'll just embed a `start` function in the wasm module | ||
executables: true, | ||
|
||
// relatively self-explanatory! | ||
exe_suffix: ".wasm".to_string(), | ||
dll_prefix: String::new(), | ||
dll_suffix: ".wasm".to_string(), | ||
linker_is_gnu: false, | ||
|
||
max_atomic_width: Some(64), | ||
|
||
// Unwinding doesn't work right now, so the whole target unconditionally | ||
// defaults to panic=abort. Note that this is guaranteed to change in | ||
// the future once unwinding is implemented. Don't rely on this as we're | ||
// basically guaranteed to change it once WebAssembly supports | ||
// exceptions. | ||
panic_strategy: PanicStrategy::Abort, | ||
|
||
// Wasm doesn't have atomics yet, so tell LLVM that we're in a single | ||
// threaded model which will legalize atomics to normal operations. | ||
singlethread: true, | ||
|
||
// no dynamic linking, no need for default visibility! | ||
default_hidden_visibility: true, | ||
|
||
// we use the LLD shipped with the Rust toolchain by default | ||
linker: Some("rust-lld".to_owned()), | ||
lld_flavor: LldFlavor::Wasm, | ||
|
||
// No need for indirection here, simd types can always be passed by | ||
// value as the whole module either has simd or not, which is different | ||
// from x86 (for example) where programs can have functions that don't | ||
// enable simd features. | ||
simd_types_indirect: false, | ||
|
||
pre_link_args, | ||
|
||
.. Default::default() | ||
} | ||
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,70 +1,48 @@ | ||
// The wasm32-unknown-unknown target is currently an experimental version of a | ||
// wasm-based target which does *not* use the Emscripten toolchain. Instead | ||
// this toolchain is based purely on LLVM's own toolchain, using LLVM's native | ||
// WebAssembly backend as well as LLD for a native linker. | ||
// | ||
// There's some trickery below on crate types supported and various defaults | ||
// (aka panic=abort by default), but otherwise this is in general a relatively | ||
// standard target. | ||
|
||
use super::{LldFlavor, LinkerFlavor, Target, TargetOptions, PanicStrategy}; | ||
//! A "bare wasm" target representing a WebAssembly output that makes zero | ||
//! assumptions about its environment. | ||
//! | ||
//! The `wasm32-unknown-unknown` target is intended to encapsulate use cases | ||
//! that do not rely on any imported functionality. The binaries generated are | ||
//! entirely self-contained by default when using the standard library. Although | ||
//! the standard library is available, most of it returns an error immediately | ||
//! (e.g. trying to create a TCP stream or something like that). | ||
//! | ||
//! This target is more or less managed by the Rust and WebAssembly Working | ||
//! Group nowadays at https://github.com/rustwasm. | ||
|
||
use super::{LldFlavor, LinkerFlavor, Target}; | ||
use super::wasm32_base; | ||
|
||
pub fn target() -> Result<Target, String> { | ||
let opts = TargetOptions { | ||
// we allow dynamic linking, but only cdylibs. Basically we allow a | ||
// final library artifact that exports some symbols (a wasm module) but | ||
// we don't allow intermediate `dylib` crate types | ||
dynamic_linking: true, | ||
only_cdylib: true, | ||
|
||
// This means we'll just embed a `start` function in the wasm module | ||
executables: true, | ||
|
||
// relatively self-explanatory! | ||
exe_suffix: ".wasm".to_string(), | ||
dll_prefix: String::new(), | ||
dll_suffix: ".wasm".to_string(), | ||
linker_is_gnu: false, | ||
|
||
max_atomic_width: Some(64), | ||
|
||
// Unwinding doesn't work right now, so the whole target unconditionally | ||
// defaults to panic=abort. Note that this is guaranteed to change in | ||
// the future once unwinding is implemented. Don't rely on this. | ||
panic_strategy: PanicStrategy::Abort, | ||
|
||
// Wasm doesn't have atomics yet, so tell LLVM that we're in a single | ||
// threaded model which will legalize atomics to normal operations. | ||
singlethread: true, | ||
let mut options = wasm32_base::options(); | ||
let clang_args = options.pre_link_args.get_mut(&LinkerFlavor::Gcc).unwrap(); | ||
|
||
// no dynamic linking, no need for default visibility! | ||
default_hidden_visibility: true, | ||
// Make sure clang uses LLD as its linker and is configured appropriately | ||
// otherwise | ||
clang_args.push("--target=wasm32-unknown-unknown".to_string()); | ||
|
||
// we use the LLD shipped with the Rust toolchain by default | ||
linker: Some("rust-lld".to_owned()), | ||
lld_flavor: LldFlavor::Wasm, | ||
// Disable attempting to link crt1.o since it typically isn't present and | ||
// isn't needed currently. | ||
clang_args.push("-nostdlib".to_string()); | ||
|
||
// No need for indirection here, simd types can always be passed by | ||
// value as the whole module either has simd or not, which is different | ||
// from x86 (for example) where programs can have functions that don't | ||
// enable simd features. | ||
simd_types_indirect: false, | ||
// For now this target just never has an entry symbol no matter the output | ||
// type, so unconditionally pass this. | ||
clang_args.push("-Wl,--no-entry".to_string()); | ||
options.pre_link_args.get_mut(&LinkerFlavor::Lld(LldFlavor::Wasm)) | ||
.unwrap() | ||
.push("--no-entry".to_string()); | ||
|
||
.. Default::default() | ||
}; | ||
Ok(Target { | ||
llvm_target: "wasm32-unknown-unknown".to_string(), | ||
target_endian: "little".to_string(), | ||
target_pointer_width: "32".to_string(), | ||
target_c_int_width: "32".to_string(), | ||
// This is basically guaranteed to change in the future, don't rely on | ||
// this. Use `not(target_os = "emscripten")` for now. | ||
target_os: "unknown".to_string(), | ||
target_env: String::new(), | ||
target_vendor: "unknown".to_string(), | ||
data_layout: "e-m:e-p:32:32-i64:64-n32:64-S128".to_string(), | ||
arch: "wasm32".to_string(), | ||
linker_flavor: LinkerFlavor::Lld(LldFlavor::Wasm), | ||
options: opts, | ||
options, | ||
}) | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.