Skip to content
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

Jump to bottom

internal/cpu: align s390x code in internal/cpu with that in x/sys/cpu #42287

Open
billotosyr opened this issue Oct 30, 2020 · 5 comments
Open

internal/cpu: align s390x code in internal/cpu with that in x/sys/cpu #42287

billotosyr opened this issue Oct 30, 2020 · 5 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. early-in-cycle A change that should be done early in the 3 month dev cycle. NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Backlog

Comments

@billotosyr
Copy link

Have recently had z/OS support added to x/sys/cpu (fixed #41984). That CL made most of the code common between z/OS and Linux. This issue tracks updating internal/cpu to include all changes from x/sys/cpu, except for zos-specific files (i.e. only the code which will be common).
@gopherbot
Copy link

Change https://golang.org/cl/266457 mentions this issue: internal/cpu: align s390x support with x/sys/cpu

@martisch
Copy link
Contributor

FYI: @billotosyr No need to open up issues for every CL if there is no algorithm or big API change or that do not need discussion or decisions.

@dmitshur dmitshur added the NeedsFix The path to resolution is known, but the work has not been done. label Oct 30, 2020
@dmitshur dmitshur changed the title internal/cpu: Align s390x code in internal/cpu with that in x/sys/cpu internal/cpu: align s390x code in internal/cpu with that in x/sys/cpu Oct 30, 2020
@dmitshur dmitshur added this to the Go1.16 milestone Oct 30, 2020
@odeke-em
Copy link
Member

odeke-em commented Feb 7, 2021

Bill, apologies that we didn’t get to review this for Go1.16. I have tagged some other reviewers for Go1.17, and I am going to punt this issue for this, as well as mark it as a release blocker.

@odeke-em odeke-em modified the milestones: Go1.16, Go1.17 Feb 7, 2021
@odeke-em odeke-em added the early-in-cycle A change that should be done early in the 3 month dev cycle. label Feb 7, 2021
@gopherbot
Copy link

This issue is currently labeled as early-in-cycle for Go 1.17.
That time is now, so a friendly reminder to look at it again.

@ianlancetaylor
Copy link
Contributor

Moving to Backlog.

@ianlancetaylor ianlancetaylor modified the milestones: Go1.17, Backlog May 4, 2021
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. early-in-cycle A change that should be done early in the 3 month dev cycle. NeedsFix The path to resolution is known, but the work has not been done.
Projects
Go Compiler / Runtime
Status: Triage Backlog
Milestone
Backlog
Development

No branches or pull requests
6 participants
@martisch @dmitshur @ianlancetaylor @odeke-em @gopherbot @billotosyr