tinygo/targets/wasm.json

{
	"llvm-target":   "wasm32-unknown-wasi",
	"cpu":           "generic",
	"build-tags":    ["tinygo.wasm"],
	"goos":          "js",
	"goarch":        "wasm",
	"linker":        "wasm-ld",
	"libc":          "wasi-libc",
	"ldflags": [
		"--allow-undefined",
		"--stack-first",
		"--no-demangle"
	],
	"emulator":      ["node", "targets/wasm_exec.js"],
	"wasm-abi":      "js"
}
all: add WebAssembly backend 6 years ago			`{`
build: normalize target triples to match Clang This commit changes a target triple like "armv6m-none-eabi" to "armv6m-unknown-unknow-eabi". The reason is that while the former is correctly parsed in Clang (due to normalization), it wasn't parsed correctly in LLVM meaning that the environment wasn't set to EABI. This change normalizes all target triples and uses the EABI environment (-eabi in the triple) for Cortex-M targets. This change also drops the `--target=` flag in the target JSON files, the flag is now added implicitly in `(*compileopts.Config).CFlags()`. This removes some duplication in target JSON files. Unfortunately, this change also increases code size for Cortex-M targets. It looks like LLVM now emits calls like __aeabi_memmove instead of memmove, which pull in slightly more code (they basically just call the regular C functions) and the calls themself don't seem to be as efficient as they could be. Perhaps this is a LLVM bug that will be fixed in the future, as this is a very common occurrence. 3 years ago			`"llvm-target": "wasm32-unknown-wasi",`
targets: add CPU property everywhere This is for consistency with Clang, which always adds a CPU flag even if it's not specified in CFLAGS. This commit also adds some tests to make sure the Clang target-cpu matches the CPU property in the JSON files. This does have an effect on the generated binaries. The effect is very small though: on average just 0.2% increase in binary size, apparently because Cortex-M3 and Cortex-M4 are compiled a bit differently. However, when rebased on top of https://github.com/tinygo-org/tinygo/pull/2218 (minsize), the difference drops to -0.1% (a slight decrease on average). 3 years ago			`"cpu": "generic",`
wasi: remove wasm build tag The wasm build tag together with GOARCH=arm was causing problems in the internal/cpu package. In general, I think having two architecture build tag will only cause problems (in this case, wasm and arm) so I've removed the wasm build tag and replaced it with tinygo.wasm. This is similar to the tinygo.riscv build tag, which is used for older Go versions that don't yet have RISC-V support in the standard library (and therefore pretend to be GOARCH=arm instead). 3 years ago			`"build-tags": ["tinygo.wasm"],`
wasm: add GOOS/GOARCH properties This was an oversight in commit 107fccb288. 6 years ago			`"goos": "js",`
			`"goarch": "wasm",`
main: use wasm-ld instead of wasm-ld-8 on macOS This commit does a few things: * remove the -8 suffix on macOS, where it is not necessary * add smoke tests for compiling wasm files on Linux and macOS 6 years ago			`"linker": "wasm-ld",`
wasi: specify wasi-libc in a different way This way is more consistent with how picolibc is specified and allows generating a helpful error message. This error message should never be generated for TinyGo binary releases, only when doing local development. 4 years ago			`"libc": "wasi-libc",`
wasm: fix .json file after compiler updates 6 years ago			`"ldflags": [`
all: switch to LLVM 8 6 years ago			`"--allow-undefined",`
wasm: set the stack at the start of linear memory This makes sure that a stack overflow will cause a "memory access out of bounds" error instead of a corruption of a global variable. Here is more background on a very similar stack overflow protection: https://blog.japaric.io/stack-overflow-protection/ 5 years ago			`"--stack-first",`
wasi: specify wasi-libc in a different way This way is more consistent with how picolibc is specified and allows generating a helpful error message. This error message should never be generated for TinyGo binary releases, only when doing local development. 4 years ago			`"--no-demangle"`
all: add WebAssembly backend 6 years ago			`],`
add wasm-abi field in TargetSpec && set generic for WASI by default (#1421) Signed-off-by: mathetake <takeshi@tetrate.io> 4 years ago			`"emulator": ["node", "targets/wasm_exec.js"],`
			`"wasm-abi": "js"`
all: add WebAssembly backend 6 years ago			`}`