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
test/fixedbugs: issue11656.go fails on s390x/z13 with SIGILL #44028
Comments
Strange that the instruction bytes are all zeroes, and not the ones written in the test. If that's the case, then it successfully wrote a value to address 0. How could it do that? You might double-check the bytes used in the s390x code. |
Change https://golang.org/cl/288278 mentions this issue: |
@randall77 it really all seem to be zeroed.
The CL288278 fixes the issue for me. I have built/"tested" it via Fedora's build system(it will get eventually GCed) without any issue(bootstrapped by beta1), including arm. I have seen the test fail for the first time there. |
What version of Go are you using (
go version
)?go1.16beta1
go1.15.6
as bootstrap compiler.
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?linux/s390x on z13
What did you do?
./run.bash
What did you expect to see?
Go testsuite passes.
What did you see instead?
This seems to be regression in the rc1, beta1 has been without this issue. There seems to be significant changes in the test case https://github.com/golang/go/blob/master/test/fixedbugs/issue11656.go pulled in to the rc1. Also it is isolated to the z13. On z14 the test passes.
The text was updated successfully, but these errors were encountered: