-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/compile: SIGBUS unaligned access on mips64 via qemu-mips64 #67160
Comments
This sounds like #46283. What about the fix for that issue isn't working here? Strange... |
Probably the rewrite of type equality code in https://go-review.googlesource.com/c/go/+/399542 |
Change https://go.dev/cl/583175 mentions this issue: |
@gopherbot please open backport issues. This looks like it started in 1.20. So maybe that CL isn't to blame? I think it would have landed in 1.21 if I'm getting my math right. |
Backport issue(s) opened: #67164 (for 1.21). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
@randall77 If I'm not mistaken my CL you mentioned would have landed in 1.19, it was merged Apr 21, 2022 and the 1.19 tree had just opened the month before (#51336 (comment)). That being said, I'm not sure if my CL introduced the bug or not. It was largely a refactoring to prepare for https://go-review.googlesource.com/c/go/+/411674 which did end up landing in 1.20. The function |
@gopherbot please open a backport issue for 1.22. |
Go version
go version go1.22.2 linux/amd64 (emulated mips64 via qemu-mips64; qemu-user pkg on most distros)
Output of
go env
in your module/workspace:What did you do?
via
-exec qemu-mips64
:What did you see happen?
What did you expect to see?
The expected program output is:
The text was updated successfully, but these errors were encountered: