cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 15:43:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Added initial warning text for bug 27961 to the WebAssembly page

Justin Clift 2018-10-04 07:04:56 +01:00
parent c39b182895
commit 6a561353fb
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
WebAssembly.md

@ -139,4 +139,18 @@ Please get involved and help drive this if you're interested in the Debugger sid
# WebAssembly in Chrome # WebAssembly in Chrome
If you run a newer version of Chrome there is a flag (`chrome://flags/#enable-webassembly-baseline`) to enable Liftoff, their new compiler, which should significantly improve load times. Further info [here](https://chinagdg.org/2018/08/liftoff-a-new-baseline-compiler-for-webassembly-in-v8/). If you run a newer version of Chrome there is a flag (`chrome://flags/#enable-webassembly-baseline`) to enable Liftoff, their new compiler, which should significantly improve load times. Further info [here](https://chinagdg.org/2018/08/liftoff-a-new-baseline-compiler-for-webassembly-in-v8/).
# Known bug
The Go 1.11 release [has a bug](https://github.com/golang/go/issues/27961) which can generate incorrect wasm code in some (rare) circumstances.
If your go code compiles to wasm ok, but gives an error in the browser like:
```
CompileError: wasm validation error: at offset 1269295: type mismatch: expression has type i64 but expected f64
```
Then you're probably hitting this bug.
The fix has been added to both the Go [1.11 release](https://github.com/golang/go/tree/release-branch.go1.11) and [master](https://github.com/golang/go/commits/master) branches, so re-compiling Go from either of those will solve the problem.