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

windows/arm: fatal error: minpc or maxpc invalid [1.15 backport] #42849

Closed
gopherbot opened this issue Nov 26, 2020 · 7 comments
Closed

windows/arm: fatal error: minpc or maxpc invalid [1.15 backport] #42849

gopherbot opened this issue Nov 26, 2020 · 7 comments
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Go1.15.8

Comments

@gopherbot
Copy link

@zx2c4 requested issue #42786 to be considered for backport to the next 1.15 minor release.

@gopherbot please backport this to 1.15
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Nov 26, 2020
@gopherbot gopherbot mentioned this issue Nov 26, 2020
Closed
@gopherbot gopherbot added this to the Go1.15.6 milestone Nov 26, 2020
@gopherbot
Copy link
Author

Change https://golang.org/cl/273567 mentions this issue: [release-branch.go1.15] cmd/link: windows/arm is all pie, so mark it as such

@zx2c4
Copy link
Contributor

zx2c4 commented Nov 26, 2020

Got this all backported, as it was a 1.15 regression from 1.14.

CC @cherrymui @jeremyfaller

@cagedmantis cagedmantis modified the milestones: Go1.15.6, Go1.15.7 Dec 3, 2020
@dmitshur
Copy link
Contributor

CL 273567 was closed. Has the status here changed @zx2c4? Thanks.

@dmitshur dmitshur added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Dec 30, 2020
@aclements
Copy link
Member

@zx2c4 , friendly ping.

@zx2c4
Copy link
Contributor

zx2c4 commented Jan 7, 2021

I had tried to backport it earlier, but it still wound up triggering, I think because some of these issues were fixed in part by the darwin work in 1.16. Then I found so many other bugs in windows/arm that only got fixed in 1.16 that I figured it wasn't worth the bother. I consider 1.16 the first release in a while with windows/arm actually supported again -- and we have the buildbot now churning away.

@aclements
Copy link
Member

Thanks for the update. @golang/osp-team , should we just close this backport issue?

@dmitshur
Copy link
Contributor

dmitshur commented Jan 7, 2021

Yes, let's do that. Thank you.

@dmitshur dmitshur closed this as completed Jan 7, 2021
@dmitshur dmitshur modified the milestones: Go1.15.7, Go1.15.8 Jan 19, 2021
@golang golang locked and limited conversation to collaborators Jan 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Go1.15.8
Development

No branches or pull requests
5 participants
@zx2c4 @cagedmantis @dmitshur @aclements @gopherbot