New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/compile: thread support for webassembly #28631

Open
sleagon opened this Issue Nov 7, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@sleagon

sleagon commented Nov 7, 2018

What version of Go are you using (go version)?

$ go version
go version go1.11.1 darwin/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/sion/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/sion/go1.X"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/6z/bfzgs4bs75bdjmr9c7dggct40000gn/T/go-build090156779=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

It is very nice to use goroutine browsers, WebAssembly Threads ready to try in Chrome 70. I found no related issues here, so i just add this issue.

What did you expect to see?

Thread feature supported in xx.wasm.

What did you see instead?

Not supported in chromium 72.

@agnivade agnivade changed the title from Thread support for webassembly in chrome 70+? to cmd/compile: thread support for webassembly Nov 7, 2018

@agnivade agnivade added this to the Unplanned milestone Nov 7, 2018

@agnivade

This comment has been minimized.

Member

agnivade commented Nov 7, 2018

I guess it would have been done anyways at some point. But thanks for filing an issue.

@neelance

This comment has been minimized.

Member

neelance commented Nov 10, 2018

Related: #28360 on the policy of adopting new WebAssembly features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment