-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/go: commit a6ff433d6a927e8ad8eaa6828127233296d12ce5 reduces concurrency in compiler #48490
Comments
This probably means we should have an integreation test to ensure that the |
So it seems the flags order change affect go/src/cmd/go/internal/work/gc.go Line 185 in 79159f2
|
Change https://golang.org/cl/351049 mentions this issue: |
Change https://golang.org/cl/351849 mentions this issue: |
So after constructing "args" variable, "gcflags" is not used anywhere. It makes the code easier to maintain, and prevent subtle bug like #48490. Change-Id: I41653536480880a8a6f9fbf6cfa8a461b6fb3208 Reviewed-on: https://go-review.googlesource.com/c/go/+/351849 Reviewed-by: Bryan C. Mills <[email protected]> Reviewed-by: Jay Conrod <[email protected]> Reviewed-by: Russ Cox <[email protected]> Run-TryBot: Bryan C. Mills <[email protected]> TryBot-Result: Go Bot <[email protected]> Trust: Cuong Manh Le <[email protected]>
Change https://golang.org/cl/353949 mentions this issue: |
After CL 353871, darwin/arm64 now do concurrent build, so enable the test for it. Updates #48490 Change-Id: I29336f6fc7d7d2f463d8ad2a620534bd7f048d2c Reviewed-on: https://go-review.googlesource.com/c/go/+/353949 Trust: Cuong Manh Le <[email protected]> Run-TryBot: Cuong Manh Le <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Bryan C. Mills <[email protected]>
Commit a6ff433 changes the way flags get passed to the compiler. As an unintended side-effect, the
-c
(for concurrency) flag seems to no longer get passed fromgo build
togo tool compile
. This can be seen in the output ofgo build -x
, and it can be felt when runningmake.bash
, which went from ~600% CPU utilization on the commit's parent to ~390% CPU utilization./cc @cuonglm @bcmills @mvdan
The text was updated successfully, but these errors were encountered: