-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
all: reopen tree for Go 1.17 development #44222
Comments
It's planned by @golang/release for this issue to begin progressing after the Go 1.16 release is issued. |
|
Change https://golang.org/cl/292709 mentions this issue: |
This CL merges the dev.regabi branch to the master branch. In the dev.regabi branch we have refactored the compiler, and laid some preliminary work for enabling a register-based ABI (issue #40724), including improved late call/return lowering, improved ABI wrapper generation, reflect call prepared for the new ABI, and reserving special registers in the internal ABI. The actual register-based ABI has not been enabled for the moment. The ABI-related changes are behind GOEXPERIMENT=regabi and currently off by default. Updates #40724, #44222. Fixes #44224. Change-Id: Id5de9f734d14099267ab717167aaaeef31fdba70
Merging dev.regabi into master (issue #44224) was resolved (thank you @cherrymui). The next item currently in the list is:
When it's done (or if plans change), please update this issue and coordinate with the people working on the next item. Thank you! |
Quick update. Merging the dev.typeparams branch will require 1) to merge master into dev.typeparams (today), 2) isolating API changes that we may need for 1.18 but not for 1.17 (next couple of days), and then 3) merging dev.typeparams into master (hopefully by end of this week). |
While we wait for dev.typeparams, it is OK for the cmd/go changes to proceed - I just checked and there are no changes in cmd/go on dev.typeparams. |
It also looks OK for the windows/arm64 changes to proceed - there is no overlap except for one if statement in cmd/compile deciding about whether arm64 frame pointers are enabled, and dev.typeparams won't be changing that. |
The |
Status update on dev.typeparams:
Currently we are trying to get x/tools tests to pass: They rely on go/parser and go/types which have changed significantly. We have fixed several failures and should be down to one or two at the most by tonight. Once x/tools passes, we can merge once more with master (should be clean) and then dev.typeparams can be merged into master. Maybe tomorrow, and hopefully before Monday. |
Status update on dev.typeparams:
Once the lsp tests are deemed ok we should be ready to go. Next steps:
|
I merged the windows/arm64 changes last night and broke a few builders. I have CLs out for those. |
@dmitshur FYI, Russ has asked me to do an early submit https://go-review.googlesource.com/c/go/+/293309 with the fix for https://golang.org/issue/44344. Hope that is ok. |
I think the guidelines should be that pure bug fixes are OK at any time. |
@thanm Yes, as Russ said that CL is a follow up to the dev.regabi merge and is okay. Thanks. |
Status update on dev.typeparams: x/tools should now be green. I tested the merge in https://golang.org/cl/293770, and all Trybots succeeded (including x/tools). To be extra careful I'll also run x/tools tests on various other builders using gomote, though I'm not actually aware of changes in dev.typeparams that would cause failures on specific builders. |
@findleyr and @griesemer are going to work on the dev.typeparams -> master merge in about an hour. (The tooling requires that no commits appear on master between the preparatory master -> dev.typeparams merge and the final dev.typeparams -> master merge, so we can help them avoid doing multiple of the first merge by not submitting anything.) Thanks! |
dev.typeparams has been merged into master. |
dev.typeparams is merged. |
If any +2'ers want to help move things along, once these reformatting CLs are in I think we can soft-open the tree. |
I've submitted what must be submitted before soft-reopening. I'm waiting for the dashboards to clear and will post when it is time. One more reformatting CL for anyone who wants it: https://go-review.googlesource.com/c/sys/+/294490. |
OK, things look stable enough on the dashboard. Thanks for the reviews. The tree is now open for bug fixes only. This is a soft reopening for the weekend, before the full re-opening Monday. The compiler underwent major surgery during the freeze in preparation for generics, Happy hacking! |
The "Current Tree Status" was updated from "Open for bug fixes only" to "Open for Go 1.17 development". I've sent an announcement to golang-dev. Closing, as this issue is resolved. Thanks everyone! |
Current Tree Status: Open for Go 1.17 development (see golang-dev announcement)
As we're getting closer to the final Go 1.16 release, we will soon need to open the tree for Go 1.17 development.
As usual, the tree will initially be open to changes that must land early. Tentatively:
internal/goversion
—this must be the very first CL to be submitted; CC @bcmillsWe will send status updates to golang-dev@ as part of this work.
This is the tracking issue for completing this task.
CC @golang/release, @ianlancetaylor.
The text was updated successfully, but these errors were encountered: