4 ms·
Because foo() gets implicitly declared as accepting int arguments, when it actually accepts a double. The double bits interpreted as an int are 0.
by WalterBright 4y ago
Because foo() gets implicitly declared as accepting int arguments, when it actually accepts a double. The double bits interpreted as an int are 0.
- edflsafoiewq 4y agoOn x64, foo(double) expects its argument in xmm0, but foo(int) expects it in rdi. So the 3 passed in rdi is ignored and it operates on whatever happened to be in xmm0.
- WalterBright 4y agoYes, you're right. Thanks for the correction. I was thinking of the Windows C ABI.