We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
master
go env
GOARCH=ppc64 GOOS=aix
go test cmd/cgo/internal/testcarchive
Various strange failures.
Many c-archive tests are failing. The argc/argv parameters are getting corrupted cause the the test binary to do unexpected things.
All tests pass, and argc/argv parameters to main not get corrupted when c-archives are linked.
main
The text was updated successfully, but these errors were encountered:
Change https://go.dev/cl/606895 mentions this issue: runtime: on aix, fix call to _cgo_sys_thread_create in _rt0_ppc64_aix_lib
runtime: on aix, fix call to _cgo_sys_thread_create in _rt0_ppc64_aix_lib
Sorry, something went wrong.
d49d0e0
@gopherbot please consider this for backport to 1.22 and 1.23, this is a bug with no workaround.
Backport issue(s) opened: #68972 (for 1.22), #68973 (for 1.23).
Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.
pmur
No branches or pull requests
Go version
master
Output of
go env
in your module/workspace:What did you do?
go test cmd/cgo/internal/testcarchive
What did you see happen?
Various strange failures.
Many c-archive tests are failing. The argc/argv parameters are getting corrupted cause the the test binary to do unexpected things.
What did you expect to see?
All tests pass, and argc/argv parameters to
main
not get corrupted when c-archives are linked.The text was updated successfully, but these errors were encountered: