-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime, cmd/compile: SIGILL during fixedbugs/issue11656.go on aix-ppc64 #44583
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
Comments
aix/ppc64 looks green on the dashboard recently. Maybe this is resolved or just rare? I'll move this to Backlog since it doesn't seem this is actively being worked on for Go 1.17 specifically. |
2022-01-06T21:38:57-c5540e5/aix-ppc64 |
Marking as release-blocker because this is showing up fairly frequently in the builders and should at least be easy to suppress. If no one is actively working on this issue, the test should be skipped on this platform to avoid masking other regressions. |
Change https://golang.org/cl/376354 mentions this issue: |
I wonder if there is some cache coherence thing? We write some bytes in memory then execute them, but the I-cache may be still holding the old content which may be an illegal instruction? |
Change https://golang.org/cl/377314 mentions this issue: |
For some reason, aix sometimes executes the bogus function body. This should never happen as it lives in a no-execute section. It might be a transient permission blip as the heap grows. Add a small function to cleanup and synchronize the icache before jumping to the bogus function to ensure it causes a panic, not SIGILL. Fixes golang#44583 Change-Id: Iadca62d82bfb70fc62088705dac42a880a1208fa Reviewed-on: https://go-review.googlesource.com/c/go/+/377314 Trust: Bryan Mills <[email protected]> Run-TryBot: Paul Murphy <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Cherry Mui <[email protected]>
2021-02-24T15:12:08-07c6583/aix-ppc64
2021-02-23T04:13:10-378f73e/aix-ppc64
CC @mknyszek @jeremyfaller @trex58
The text was updated successfully, but these errors were encountered: