gh-mirror/mikepaul-LuaJIT
1
0
Fork 0
mirror of https://github.com/LuaJIT/LuaJIT.git synced 2025-02-08 07:34:07 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Don't count tail calls towards loop unroll limit.

Browse Source
This commit is contained in:
Andy Wingo 2016-01-13 11:58:40 +01:00
parent 3d4c9f9639
commit 476ea172a7
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/lj_record.c
View File

@ -651,8 +651,14 @@ void lj_record_tailcall(jit_State *J, BCReg func, ptrdiff_t nargs)
memmove(&J->base[-1], &J->base[func], sizeof(TRef)*(J->maxslot+1)); memmove(&J->base[-1], &J->base[func], sizeof(TRef)*(J->maxslot+1));
/* Note: the new TREF_FRAME is now at J->base[-1] (even for slot #0). */ /* Note: the new TREF_FRAME is now at J->base[-1] (even for slot #0). */
/* Tailcalls can form a loop, so count towards the loop unroll limit. */ /* Tailcalls can form a loop, so count towards the loop unroll limit. */
if (++J->tailcalled > J->loopunroll)
lj_trace_err(J, LJ_TRERR_LUNROLL); J->tailcalled++;
/* Although it's true that tail calls can form a loop, the Lua programming
** idiom does not encourage this. Instead of counting tail calls towards the
** unroll limit and potentially causing important traces without loops to
** abort, eventually blacklist, and fall back to the interpreter, just rely on
** JIT_P_maxrecord to catch runaway tail-call loops. */
} }
/* Check unroll limits for down-recursion. */ /* Check unroll limits for down-recursion. */