|
|
|
|
|
|
by amscanne
2124 days ago
|
|
|
This is a total red herring. I don't know why the numbers are consistently different for the different programs, but the compiler is completely optimizing out the function call in both cases. Consider the example where you do two prints:
https://play.golang.org/p/Y1GUutEQkzx Here is the compiled object code, which is identical for true and false:
main.go:15 0x49b640 64488b0c25f8ffffff MOVQ FS:0xfffffff8, CX
main.go:15 0x49b649 483b6110 CMPQ 0x10(CX), SP
main.go:15 0x49b64d 7624 JBE 0x49b673
main.go:15 0x49b64f 4883ec08 SUBQ $0x8, SP
main.go:15 0x49b653 48892c24 MOVQ BP, 0(SP)
main.go:15 0x49b657 488d2c24 LEAQ 0(SP), BP
main.go:16 0x49b65b 0f1f440000 NOPL 0(AX)(AX*1)
main.go:16 0x49b660 e89bfeffff CALL main.printStats(SB)
main.go:21 0x49b665 e896feffff CALL main.printStats(SB)
main.go:22 0x49b66a 488b2c24 MOVQ 0(SP), BP
main.go:22 0x49b66e 4883c408 ADDQ $0x8, SP
main.go:22 0x49b672 c3 RET Notice how there's nothing between the printStats calls? |
|
|