You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case, tail-call optimization doesn't apply as there is no stack entry to bypass. However, it should still behave the same as the original call (which is inlined), terminated by a return statement, when no tail-call ois possible.
This should at the very least, generate the following rather than invalid code:
call 0xC0
ret
or generate an error, failing that.
Potentially if tail-calls get optimized at the IR level (which is after inline functions are expanded), then this could generate the more optimal
jp 0xC0
branch instruction instead.
The text was updated successfully, but these errors were encountered:
Currently it is not possible to tail call an inline function. It will compile but generate incorrect code.
In this case, tail-call optimization doesn't apply as there is no stack entry to bypass. However, it should still behave the same as the original call (which is inlined), terminated by a return statement, when no tail-call ois possible.
This should at the very least, generate the following rather than invalid code:
or generate an error, failing that.
Potentially if tail-calls get optimized at the IR level (which is after inline functions are expanded), then this could generate the more optimal
branch instruction instead.
The text was updated successfully, but these errors were encountered: