wait, why is this bad? seems like a good thing to me. doesn't Go also promote some of these values to the heap as a result of escape analysis?
-
-
-
Because it adds memory traffic for no reason.
- 7 more replies
New conversation -
-
-
From Go team's point of view: for I/O bound programs that's an acceptable hit, and one avoids futzing with register allocators for a decade or two
-
It’s not a pure stack machine, it allocates resisters inside functions! But I’m not surprised if they decided against the hairball of the x64 abi calling convention. If so, suspect partly motivated by the pointer rewriting phase of stack growth, or stack switching.
- 5 more replies
New conversation -
-
-
All architectures right?
-
I think so, but not sure.
- 3 more replies
New conversation -
-
-
This Tweet is unavailable.
-
“Instructions, registers, and assembler directives are always in UPPER CASE to remind you that assembly programming is a fraught endeavor.”
End of conversation
-
-
-
Is that due to the weird split between x-8(SP) and -8(SP) in Go ASM?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
So go compiles code poorly in manifold wayssss. Yup.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
