-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/internal/types: concurrent map read and map write while compiling #21352
Comments
CC @mdempsky Would be nice to figure out the cause in case this affects 1.9. |
It believe affects 1.9, GO386=387 only. I'll try to send a CL soon. |
Change https://golang.org/cl/54091 mentions this issue: |
Change https://golang.org/cl/54090 mentions this issue: |
I think CL 54090 should be cherry-picked to 1.9. (Thanks so very much for noticing and filing an issue, @martisch.) The alternative for 1.9 is to disable concurrent compilation for GO386=387 in cmd/go and cmd/compile, but I think the proper fix is very low risk, perhaps even lower risk than the alternative. |
I concur, 54090 should be cherry-picked into 1.9. |
Re-opening for cherry-pick to 1.9. |
CC @broady |
Updates #21352 Change-Id: If21342f30be32e25840b4072b932a6d4257b420d Reviewed-on: https://go-review.googlesource.com/54091 Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Avelino <t@avelino.xxx> Reviewed-by: Matthew Dempsky <mdempsky@google.com>
Change https://golang.org/cl/55970 mentions this issue: |
…backend [This is a cherry-pick of CL 54090 to the 1.9 release branch.] gc.Sysfunc must not be called concurrently. We set up runtime routines used by the backend prior to doing any backend compilation. I missed the 387 ones; fix that. Sysfunc should have been unexported during 1.9. I will rectify that in a subsequent CL. Fixes #21352 Change-Id: I485bb1867b46d8e5cf64bc820b8963576dc16174 Reviewed-on: https://go-review.googlesource.com/55970 Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Keith Randall <khr@golang.org>
one builder failed with what it seems to be a map read / write race during compilation:
https://build.golang.org/log/95ffcbbfdfe3e328d735db12f2127b1dcf1ab17c
at tip 64bd2c4
While the read location seems clear the write location does not seem to be in the trace.
Flake or map in a bad state?
/cc @josharian
The text was updated successfully, but these errors were encountered: