Re: [go-nuts] Why can runtime.procyield declare its argument stack size to be zero?

2018-10-16 Thread Jeffrey Baker
Thanks. Now I feel a bit less crazy. -jwb On Tue, Oct 16, 2018 at 5:14 PM Ian Lance Taylor wrote: > On Thu, Oct 11, 2018 at 3:01 PM, Jeffrey Baker wrote: > > > > I'm trying to learn how to safely use this asm, and I don't understand > some > > of the existing asm in the runtime package. From

Re: [go-nuts] Why can runtime.procyield declare its argument stack size to be zero?

2018-10-16 Thread Ian Lance Taylor
On Thu, Oct 11, 2018 at 3:01 PM, Jeffrey Baker wrote: > > I'm trying to learn how to safely use this asm, and I don't understand some > of the existing asm in the runtime package. From amd64.s: > > TEXT runtime·procyield(SB),NOSPLIT,$0-0 > MOVL cycles+0(FP), AX > > My understanding of $0-0 is it'

[go-nuts] Why can runtime.procyield declare its argument stack size to be zero?

2018-10-11 Thread Jeffrey Baker
I'm trying to learn how to safely use this asm, and I don't understand some of the existing asm in the runtime package. From amd64.s: TEXT runtime·procyield(SB),NOSPLIT,$0-0 MOVL cycles+0(FP), AX My understanding of $0-0 is it's supposed to indicate the sizes of the arguments, in this case wou