rust/tests/run-make/wasm-panic-small/Makefile

include ../tools.mk

# only-wasm32-bare

all:
	$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg a
	wc -c < $(TMPDIR)/foo.wasm
	[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "1024" ]
	$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg b
	wc -c < $(TMPDIR)/foo.wasm
	[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "5120" ]
	$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg c
	wc -c < $(TMPDIR)/foo.wasm
	[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "5120" ]
	$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg d
	wc -c < $(TMPDIR)/foo.wasm
	[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "5120" ]
move `tools.mk` to run-make apparently I missed some tests in the last commit. Rather than having dozens of tests use the long version, use the short version in `run-make` and the long version in `run-make-fulldeps` (which is now only three tests) 2023-03-30 07:58:50 -05:00			`include ../tools.mk`
std: Minimize size of panicking on wasm This commit applies a few code size optimizations for the wasm target to the standard library, namely around panics. We notably know that in most configurations it's impossible for us to print anything in wasm32-unknown-unknown so we can skip larger portions of panicking that are otherwise simply informative. This allows us to get quite a nice size reduction. Finally we can also tweak where the allocation happens for the `Box<Any>` that we panic with. By only allocating once unwinding starts we can reduce the size of a panicking wasm module from 44k to 350 bytes. 2018-03-29 14:59:13 -07:00
Upgrade Emscripten targets to use upstream LLVM backend - Compatible with Emscripten 1.38.46-upstream or later upstream. - Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the old incorrect wasm32 C call ABI with the correct one, preserving the old one as wasm32_bindgen_compat for wasm-bindgen compatibility. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Uses EMCC_CFLAGS on CI to avoid the timeout problems with #63649. 2019-08-16 22:08:01 -07:00			`# only-wasm32-bare`
use ignore directives for run-make tests This makes the tests easier to read, and makes it possible to tell which tests aren't being run on the host platform. Fixes #56704. 2019-01-06 16:27:57 -05:00
std: Minimize size of panicking on wasm This commit applies a few code size optimizations for the wasm target to the standard library, namely around panics. We notably know that in most configurations it's impossible for us to print anything in wasm32-unknown-unknown so we can skip larger portions of panicking that are otherwise simply informative. This allows us to get quite a nice size reduction. Finally we can also tweak where the allocation happens for the `Box<Any>` that we panic with. By only allocating once unwinding starts we can reduce the size of a panicking wasm module from 44k to 350 bytes. 2018-03-29 14:59:13 -07:00			`all:`
std: Avoid allocating panic message unless needed This commit removes allocation of the panic message in instances like `panic!("foo: {}", "bar")` if we don't actually end up needing the message. We don't need it in the case of wasm32 right now, and in general it's not needed for panic=abort instances that use the default panic hook. For now this commit only solves the wasm use case where with LTO the allocation is entirely removed, but the panic=abort use case can be implemented at a later date if needed. 2018-04-06 14:22:13 -07:00			`$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg a`
std: Minimize size of panicking on wasm This commit applies a few code size optimizations for the wasm target to the standard library, namely around panics. We notably know that in most configurations it's impossible for us to print anything in wasm32-unknown-unknown so we can skip larger portions of panicking that are otherwise simply informative. This allows us to get quite a nice size reduction. Finally we can also tweak where the allocation happens for the `Box<Any>` that we panic with. By only allocating once unwinding starts we can reduce the size of a panicking wasm module from 44k to 350 bytes. 2018-03-29 14:59:13 -07:00			`wc -c < $(TMPDIR)/foo.wasm`
			[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "1024" ]
std: Avoid allocating panic message unless needed This commit removes allocation of the panic message in instances like `panic!("foo: {}", "bar")` if we don't actually end up needing the message. We don't need it in the case of wasm32 right now, and in general it's not needed for panic=abort instances that use the default panic hook. For now this commit only solves the wasm use case where with LTO the allocation is entirely removed, but the panic=abort use case can be implemented at a later date if needed. 2018-04-06 14:22:13 -07:00			`$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg b`
			`wc -c < $(TMPDIR)/foo.wasm`
			[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "5120" ]
			`$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg c`
			`wc -c < $(TMPDIR)/foo.wasm`
			[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "5120" ]
std: Improve codegen size of accessing TLS Some code in the TLS implementation in libstd stores `Some(val)` into an `&mut Option<T>` (effectively) and then pulls out `&T`, but it currently uses `.unwrap()` which can codegen into a panic even though it can never panic. With sufficient optimizations enabled (like LTO) the compiler can see through this but this commit helps it along in normal mode (`--release` with Cargo by default) to avoid codegen'ing the panic path. This ends up improving the optimized codegen on wasm by ensuring that a call to panic pulling in more file size doesn't stick around. 2018-10-28 08:26:47 -07:00			`$(RUSTC) foo.rs -C lto -O --target wasm32-unknown-unknown --cfg d`
			`wc -c < $(TMPDIR)/foo.wasm`
			[ "`wc -c < $(TMPDIR)/foo.wasm`" -lt "5120" ]