-
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
runtime: unaligned atomic access to m.procid on 32-bit (arm, 386, ...) #52810
Labels
Comments
Maybe a regression from 8ac23a1 which added a word to |
It broke as of 0a5fae2 (https://golang.org/cl/383434) on Feb 15. It's fine at 0a5fae2's parent (0b321c9).
/cc @prattmic |
Sigh. And now I found dup bug #51776. Closing. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Repro, on Go 1.18.1:
Run on a Raspberry Pi (where it was first found) or really any 32-bit device or GOARCH=386 on amd64 and:
That os_linux.go:816 is:
The
m
type is:Looks like
gobuf
is 7 words wide, which putsprocid
at 9 words offset? (not 64-bit aligned)Didn't look too closely.
/cc @maisem @raggi @golang/runtime
The text was updated successfully, but these errors were encountered: