about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/example/alloc_example.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2021-11-18 17:19:27 +0000
committerbors <bors@rust-lang.org>2021-11-18 17:19:27 +0000
commitb6f580acc0ce233d5c4d1f9680d354fded88b824 (patch)
tree3b8577cde0c88686f2cca92916f7e60dee8ecdeb /compiler/rustc_codegen_gcc/example/alloc_example.rs
parent6414e0b5b308d3ae27da83c6a25098cc8aadc1a9 (diff)
parentaf217f7f78762184b66957aa87c8d4493d83e86a (diff)
downloadrust-b6f580acc0ce233d5c4d1f9680d354fded88b824.tar.gz
rust-b6f580acc0ce233d5c4d1f9680d354fded88b824.zip
Auto merge of #90382 - alexcrichton:wasm64-libstd, r=joshtriplett
std: Get the standard library compiling for wasm64

This commit goes through and updates various `#[cfg]` as appropriate to
get the wasm64-unknown-unknown target behaving similarly to the
wasm32-unknown-unknown target. Most of this is just updating various
conditions for `target_arch = "wasm32"` to also account for `target_arch
= "wasm64"` where appropriate. This commit also lists `wasm64` as an
allow-listed architecture to not have the `restricted_std` feature
enabled, enabling experimentation with `-Z build-std` externally.

The main goal of this commit is to enable playing around with
`wasm64-unknown-unknown` externally via `-Z build-std` in a way that's
similar to the `wasm32-unknown-unknown` target. These targets are
effectively the same and only differ in their pointer size, but wasm64
is much newer and has much less ecosystem/library support so it'll still
take time to get wasm64 fully-fledged.
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions