-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: disabling inlining breaks on arm64, ppc64 #11482
Comments
Moving to Go 1.6, since arm64 and ppc64 are only preview releases in 1.5. |
This happens on ppc64 too. |
Looks like a missing nosplit. It would be nice to find out what exactly the pc= in the morebuf line corresponds to. That is, the output above says:
In that case it would be nice to know what |
These are methods that are "obviously" going to get inlined -- until you build with -l, when they can trigger a stack split at a bad time. Fixes golang#11482 Change-Id: Ia065c385978a2e7fe9f587811991d088c4d68325
Ah thanks for the hint -- it was one of the {g,m,p}uintptr methods. Just sent a CL marking them all nosplit. |
CL https://golang.org/cl/17165 mentions this issue. |
For example:
I guess something that is usually inlined needs to be marked nosplit?
The text was updated successfully, but these errors were encountered: