Zxilly bcec5f1540 syscall,misc/wasm: fix path expansion on non-unix platforms ... When running a go binary compiled to wasm using node.js on a Windows platform, the absolute path passed in is also incorrectly forced to expand. For example: E:\Project\CS_Project\gsv\testdata\result.gob.gz will results to open C:\Users\zxilly\AppData\Local\wasm-exec\go1.23rc1\E:\Project\CS_Project\gsv\testdata\result.gob.gz: No such file or directory C:\Users\zxilly\AppData\Local\wasm-exec\go1.23rc1 is the place of wasm_exec_node.js Fixes: #68820 Change-Id: Ic30c6242302f8915ac1b8ea9f24546935cbb791e GitHub-Last-Rev: f35ff1a2ee GitHub-Pull-Request: golang/go#68255 Reviewed-on: https://go-review.googlesource.com/c/go/+/595797 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>		2024-08-09 21:22:25 +00:00
..
go_js_wasm_exec
go_wasip1_wasm_exec	misc/wasm: drop wasmtime < 14 support	2024-04-11 17:09:10 +00:00
wasm_exec_node.js	syscall,misc/wasm: fix path expansion on non-unix platforms	2024-08-09 21:22:25 +00:00
wasm_exec.html
wasm_exec.js	syscall,misc/wasm: fix path expansion on non-unix platforms	2024-08-09 21:22:25 +00:00