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

cmd/internal/objabi, cmd/link: direct calls not correctly identified on riscv64 [1.20 backport] #63166

Closed
gopherbot opened this issue Sep 22, 2023 · 1 comment
Labels
CherryPickCandidate Used during the release process for point releases
Milestone

Comments

@gopherbot
Copy link

@ianlancetaylor requested issue #62465 to be considered for backport to the next 1.20 minor release.

@gopherbot Please open backport to 1.21.

This is a build failure with no straightforward workaround. It is a regression from 1.20.

@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Sep 22, 2023
@gopherbot gopherbot added this to the Go1.20.9 milestone Sep 22, 2023
@ianlancetaylor
Copy link
Contributor

I wrote the backport comment poorly. No 1.20 backport is required.

@ianlancetaylor ianlancetaylor closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2023
@ianlancetaylor ianlancetaylor changed the title cmd/compile,runtime: write barrier issue on riscv64 [1.20 backport] cmd/internal/objabi, cmd/link: direct calls not correctly identified on riscv64 [1.20 backport] Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CherryPickCandidate Used during the release process for point releases
Projects
None yet
Development

No branches or pull requests

2 participants