-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: illegal instruction on mips64le #43045
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
There is nothing wrong to jump to a NOP. The question is why it SIGILLs at a NOP instruction. |
I make Go net.test by 10000 times it all passed.
And it's totally fined. |
There was another SIGILL in https://build.golang.org/log/6d63d3ca732b0518bb86e5ea20b962b0b4091ea9:
Do you think that's related, or a separate issue? |
Could be Does this happen on other mips64 machines, or just @mengzhuo 's? |
@randall77 It should be just my machine ( No ECC and some old DDR3 memory from other PC) |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
maybe
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
https://build.golang.org/log/65667e5916fe3585b16aade700588c65c1f70c87
What did you expect to see?
all test passed
What did you see instead?
I rebuilded the code and checked the 0x12004d7f8
Maybe it's async preempted with wrong quatum value some where in the compiler since it jumps to NOP.
It's more weird that runtime.findrunable shouldn't be preempted.
@cherrymui @randall77
The text was updated successfully, but these errors were encountered: