opensources/lua - lua - Gitea: Git with home nas server

Commit Graph

Author	SHA1	Message	Date
Roberto Ierusalimschy	3f253f116e	Test for dead coroutine moved to 'lua_resume' The test for dead coroutines done in the 'coro' library was moved to 'lua_resume', in the kernel, which already does other similar tests.	6 years ago
Roberto Ierusalimschy	389116d8ab	Coroutines do not unwind the stack in case of errors Back to how it was, a coroutine does not unwind its stack in case of errors (and therefore do not close its to-be-closed variables). This allows the stack to be examined after the error. The program can use 'coroutine.kill' to close the variables. The function created by 'coroutine.wrap', however, closes the coroutine's variables in case of errors, as it is impossible to examine the stack any way.	6 years ago
Roberto Ierusalimschy	0443ad9e28	LUAI_MAXCCALLS renamed LUAI_MAXCSTACK The limit LUAI_MAXCCALLS was renamed LUAI_MAXCSTACK, which better represents its meaning. Moreover, its definition was moved to 'luaconf.h', given its importance now that Lua does not use a "stackless" implementation.	6 years ago
Roberto Ierusalimschy	4ace93ca65	No more to-be-closed functions To-be-closed variables must contain objects with '__toclose' metamethods (or nil). Functions were removed for several reasons: * Functions interact badly with sandboxes. If a sandbox raises an error to interrupt a script, a to-be-closed function still can hijack control and continue running arbitrary sandboxed code. * Functions interact badly with coroutines. If a coroutine yields and is never resumed again, its to-be-closed functions will never run. To-be-closed objects, on the other hand, will still be closed, provided they have appropriate finalizers. * If you really need a function, it is easy to create a dummy object to run that function in its '__toclose' metamethod. This comit also adds closing of variables in case of panic.	6 years ago
Roberto Ierusalimschy	ba7da13ec5	Changes in the control of C-stack overflow * unification of the 'nny' and 'nCcalls' counters; * external C functions ('lua_CFunction') count more "slots" in the C stack (to allow for their possible use of buffers) * added a new test script specific for C-stack overflows. (Most of those tests were already present, but concentrating them in a single script easies the task of checking whether 'LUAI_MAXCCALLS' is adequate in a system.)	6 years ago
Roberto Ierusalimschy	fdc25a1ebf	New functions 'lua_resetthread' and 'coroutine.kill' New functions to reset/kill a thread/coroutine, mainly (only?) to close any pending to-be-closed variable. ('lua_resetthread' also allows a thread to be reused...)	6 years ago
Roberto Ierusalimschy	3b06f983ae	Details - in 'luaB_tonumber', do not need to "checkany" when argument is a number. - in 'lua_resume', the call to 'luaD_rawrunprotected' cannot return a status equal to -1.	6 years ago
Roberto Ierusalimschy	7e63d3da02	Some bugs with stack reallocation by 'luaF_close' (Long time without testing with '-DHARDSTACKTESTS'...) With the introduction of to-be-closed variables, calls to 'luaF_close' can move the stack, but some call sites where keeping pointers to the stack without correcting them.	6 years ago
Roberto Ierusalimschy	34840301b5	To-be-closed variables in the C API	6 years ago
Roberto Ierusalimschy	c90176f969	Complete implementation of to-be-closed variables	6 years ago
Roberto Ierusalimschy	bd96330d03	First "complete" implementation of to-be-closed variables Still missing: - handling of memory errors when creating upvalue (must run closing method all the same) - interaction with coroutines	6 years ago
Roberto Ierusalimschy	4cd1f4aac0	Towards "to closed" local variables Start of the implementation of "scoped variables" or "to be closed" variables, local variables whose '__close' (or themselves) are called when they go out of scope. This commit implements the syntax, the opcode, and the creation of the corresponding upvalue, but it still does not call the finalizations when the variable goes out of scope (the most important part). Currently, the syntax is 'local scoped name = exp', but that will probably change.	6 years ago
Roberto Ierusalimschy	b114c7d487	Added "cost" for the use of C stack by a coroutine invocation. Resuming a coroutine uses more C stack than other operations (such as function calls or recursive syntax). So, to avoid stack overflow in recursive coroutine invocations, either LUAI_MAXCCALLS must be too small or a coroutine invocation must "pay" a higher price. New constant LUAL_COROCSTK ("COROutine C STaK") defines how much is this price.	6 years ago
Roberto Ierusalimschy	96f9643f33	Bug: wrong 'nCcalls' when resuming a coroutine The counter 'nCcalls' now includes the number of CallInfo structures pre-allocated (so that these "potential" C calls can be made without checking 'nCcalls'). So, when copying this value from a thread to another, in 'lua_resume', it must be corrected to the number of CallInfo structures in the thread being resumed.	6 years ago
Roberto Ierusalimschy	34aa0c5bd7	new macros 'likely'/'unlikely' with hints for jump predictions (used only in errors for now)	7 years ago
Roberto Ierusalimschy	02ed0b2c30	in 'luaD_poscall', there is no need to compute 'firstResult' when 'nres==0'	7 years ago
Roberto Ierusalimschy	4907444db9	'fTransfer' -> 'ftransfer' / 'nTransfer' -> 'ntransfer' (keep the standard of names in lower case)	7 years ago
Roberto Ierusalimschy	6480e73599	details (avoid using non-C89 '//' comment)	7 years ago
Roberto Ierusalimschy	8c429311a3	typo in comment	7 years ago
Roberto Ierusalimschy	ef8263f81f	better names for macros for tags and types. rttype -> rawtt; ttyperaw -> withvariant; ttype -> ttypetag; tnov -> ttype	7 years ago
Roberto Ierusalimschy	422318f677	two new fields 'fTransfer'/'nTransfer' in 'lua_Debug' structure (for information about values being given and returned in function calls)	7 years ago
Roberto Ierusalimschy	104d249ffb	in return hook, 'top' must be corrected only if smaller than 'ci->top'. (It may be larger when returning multiple values, and then it must be larger to preserve that stack slice.)	7 years ago
Roberto Ierusalimschy	0682fe8169	some simplifications/optimizations in returns from Lua functions	7 years ago
Roberto Ierusalimschy	b1379936cf	vararg back to '...' (but with another implementation) new implementation should have zero overhead for non-vararg functions	7 years ago
Roberto Ierusalimschy	4e0de3a43c	details	7 years ago
Roberto Ierusalimschy	318a9a5859	new opcode 'PREPVARARG' (avoids test for vararg function in all function calls)	7 years ago
Roberto Ierusalimschy	51280ef2ad	call hooks for Lua functions called by 'luaV_execute'	7 years ago
Roberto Ierusalimschy	dc0ab1e8ca	warnings in VS (implicit casts from ptrdiff_t to int)	7 years ago
Roberto Ierusalimschy	89110986d7	bug in tailcall of vararg functions (when adjusting missing parameters)	7 years ago
Roberto Ierusalimschy	53979dfe0d	calling a vararg function needs to check GC (because it creates a new table)	7 years ago
Roberto Ierusalimschy	ab0a851db4	'luaD_tryfuncTM' can ensure it does not change the stack	7 years ago
Roberto Ierusalimschy	28323aeaa6	by-one error when filling missing arguments in a tail call	7 years ago
Roberto Ierusalimschy	8691612f01	when calling a hook, cannot decrease 'ci->top' (to preserve stack size if the stack is reallocated)	7 years ago
Roberto Ierusalimschy	1d5b885437	when running Lua code, there is no need to keep 'L->top' "correct"; set it only when needed.	7 years ago
Roberto Ierusalimschy	4dc0be950a	new macro 'isLuacode' (to distinguish regular Lua code from hooks, where C code can run inside a Lua function).	7 years ago
Roberto Ierusalimschy	b3f924bc69	'Proto->numparams' does not include vararg parameter (one less subtraction when calling functions...)	7 years ago
Roberto Ierusalimschy	725c15a4ca	when shrinking stack, always shrinks the CI list. (Stack overflow is not corelated to CI overflow anymore.)	7 years ago
Roberto Ierusalimschy	bfb88e99e9	'luaD_growstack' cannot raise any errors when 'raiseerror' is false (+ some comments)	7 years ago
Roberto Ierusalimschy	e663a24ab0	more freedom in handling memory-allocation errors (not all allocations automatically raise an error), which allows fixing a bug when resizing a table.	7 years ago
Roberto Ierusalimschy	e0bece77d6	detail	7 years ago
Roberto Ierusalimschy	c766e4103d	'luaV_execute' gets call info as extra argument (it is always available on call sites)	7 years ago
Roberto Ierusalimschy	194a4f9710	small simplifications in 'luaD_poscall'	7 years ago
Roberto Ierusalimschy	196c87c9ce	no more 'stackless' implementation; 'luaV_execute' calls itself recursively to execute function calls. 'unroll' continues all executions suspended by an yield (through a long jump)	7 years ago
Roberto Ierusalimschy	14c3aa12b5	more direct implementation for tail calls.	7 years ago
Roberto Ierusalimschy	5440b42f43	using 'trap' to stop 'luaV_execute' when necessary (tracing and to update its copy of 'base' when the stack is reallocated)	7 years ago
Roberto Ierusalimschy	7d4828cc9f	avoid accessing wrong union field	7 years ago
Roberto Ierusalimschy	ad0704e40c	back to 'CallInfo' (no gains with its removal)	7 years ago
Roberto Ierusalimschy	93fd67b793	no more 'CallInfo' structure	7 years ago
Roberto Ierusalimschy	6bb3e40a8d	'lua_Debug' not using 'CallInfo'	7 years ago
Roberto Ierusalimschy	472c560705	no more useful fields in CallInfo	7 years ago

1 2 3 4 5 ...

445 Commits (279c3a6961c60252f0368fdea889caf977f85fe0)