<div dir="ltr"><div><div><div><div>AFAICT, cDigitCompare:with:len: is inlined by clang.<br>But the interpreterProxy messages are not inlined, but it's not really amazing, these are different units of compilation.<br>The procedure I used for checking was:<br><br>vim ../common/Makefile.flags (add option -S to CFLAGS)<br>touch ../../src/plugins/LargeIntegers/LargeIntegers.c<br>mvm -f<br>less build/LargeIntegers/LargeIntegers.o<br><br></div>And you are certainly right, compared to a few bit ops, the function calls/return/stack handling are expensive.<br></div>So inlining should make a measurable difference for "small" large integers.<br></div>I was biased by giant integers which is more what I'm after (tight loops)<br><br></div>Nicolas<br><div><div><div><br><div><div><div class="gmail_extra"><div class="gmail_quote">2016-04-17 0:59 GMT+02:00 Levente Uzonyi <span dir="ltr"><<a href="mailto:leves@caesar.elte.hu" target="_blank">leves@caesar.elte.hu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Hi Nicolas,<br>
<br>
It's been a while I optimized C programs, but I'm pretty sure function calls cost a lot compared to a few direct instructions (e.g. isIntegerObject).<span><font color="#888888"><br>
<br>
Levente<br>
</font></span></blockquote></div><br></div></div></div></div></div></div></div>