> On previous versions the assembly output reported the base register as FP
but the offset was from SP.
That's it! Go 1.8 had a bug. ;)
Thanks
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving
In the assembly output here:
https://drive.google.com/open?id=0B63rdrZtwIE9R3M4cGxrSFhmT00
some jump instructions have 2 operands. What are their semantics?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and
Should not the first parameter of a function be passed in 0(FP)? See this
example assembly (produced by go tool compile -S), where 0(FP) gets skipped
over and the argument is apparently loaded from 8(FP):
https://drive.google.com/open?id=0B63rdrZtwIE9dHZqWmoxdXIzNnc
Another confusing thing is
On Friday, 2 December 2016 11:55:59 UTC+1, nsa...@gmail.com wrote:
>
> Is there a summary somewhere of the general rules determining when
> do functions get inlined?
>
> Specifically, it should always be a good decision to inline a
> function that is only called from one place in the code (that
Is there a summary somewhere of the general rules determining when
do functions get inlined?
Specifically, it should always be a good decision to inline a
function that is only called from one place in the code (that is, a
non-reused function). Do such (at least non-exported ones)
functions get
If it's still too much a bit can be saved on code size by disabling bounds
checking.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
