cherrymui
cherrymui
@dhalman I think you can try using `go build`'s `-x` flag, e.g. ``` go build -x -trimpath -buildmode=plugin -o ``` to print out how the go command invokes the compiler...
Seems this hasn't happened for quite some time (the test is not skipped on darwin).
This is different from #39524 . We switch stacks at Go/C boundaries. Go code runs on goroutine stacks (typically small), whereas C code runs on system stacks (typically large). Since...
@steeve Sorry, I'm not sure exactly what you're planning to do, and why `go:systemstack` is relevant here. `go:systemstack` only enforces the marked function must run on the system stack (i.e....
> IMO we should get rid of that heuristic and just use NOFRAME if a runtime function would be messed up be frame pointer I think that is a good...
I agree that longjmp is not really a good analogy because it could be an actual context switch (although it could be used to implement a temporary stack transition like...
For profile, maybe we want to always include the wrapper frame, so it matches more closely to what actually happened at runtime? Not sure if this can be done easily...
I agree that `runtime_expandFinalInlineFrame` would be the wrong play. I'm just wondering if we could instead include the wrapper frames consistently.
Thanks for the issue and the CL! I think it is safe for backport. We usually don't backport performance stuff, but this is a new feature and it could cause...
They look like OOM kill. How much memory does the builder have? Does the build run in parallel with other programs or containers?