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

Commit Graph

Author	SHA1	Message	Date
Roberto Ierusalimschy	0acd55898d	Added gcc option '-Wconversion' No warnings for standard numerical types. Still pending alternative numerical types.	3 months ago
Roberto Ierusalimschy	15231d4fb2	'nresults' moved into 'callstatus' That gives us more free bits in 'callstatus', for future use.	4 months ago
Roberto Ierusalimschy	55ac40f859	Cleaning of llimits.h Several definitions that don't need to be "global" (that is, that concerns only specific parts of the code) moved out of llimits.h, to more appropriate places.	5 months ago
Roberto Ierusalimschy	9fa63a6268	Some 'unsigned int' changed to 'unsigned' 'unsigned int' is too long sometimes. (We already write 'long' instead of 'long int'...)	8 months ago
Roberto Ierusalimschy	7360f8d0fd	Removed deprecated function 'setcstacklimit'	9 months ago
Roberto Ierusalimschy	17e0c29d9b	Clear interface between references and predefines The reference system has a defined way to add initial values to the table where it operates.	10 months ago
Roberto Ierusalimschy	8eb0abc9db	Removed uses of LUA_NUMTAGS That constant was already deprecated (see commit `6aabf4b15e`).	10 months ago
Roberto Ierusalimschy	e2cc179454	New option "setparms" for 'collectgarbage' The generational mode also uses the parameters for the incremental mode in its major collections, so it should be easy to change those parameters without having to change the GC mode.	11 months ago
Roberto Ierusalimschy	ad0ea7813b	GC parameters encoded as floating-point bytes This encoding brings more precision and a larger range for these parameters.	11 months ago
Roberto Ierusalimschy	925fe8a0f2	First criteria for shifts minor<->major	11 months ago
Roberto Ierusalimschy	63d68bd657	Comments detailing the ages for generational GC Plus other comments and small details.	11 months ago
Roberto Ierusalimschy	43c8e5bded	Full abstraction for representation of array values	1 year ago
Roberto Ierusalimschy	9b4f39ab14	More disciplined use of 'getstr' and 'tsslen' We may want to add other string variants in the future; this change documents better where the code may need to handle those variants.	1 year ago
Roberto Ierusalimschy	9be74ccc21	Several functions turned 'static' Several functions that were already being used only inside their own file have been declared as 'static'.	1 year ago
Roberto Ierusalimschy	6443185167	"Emergency" new version 5.4.6 'lua_resetthread' is back to its original signature, to avoid incompatibilities in the ABI between releases of the same version. New function 'lua_closethread' added with the "correct" signature.	2 years ago
Roberto Ierusalimschy	5a04f1851e	New function 'luaL_makeseed' This function unifies code from 'lua_newstate', 'math.randomseed', and 'table.sort' that tries to create a value with a minimum level of randomness.	2 years ago
Roberto Ierusalimschy	5d8b5b9290	Changed signal of GC debt Positive debts seems more natural then negative ones.	2 years ago
Roberto Ierusalimschy	40565b4a08	Revamp of GC parameters More uniformity when handling GC parameters + avoid divisions by 100 when applying them.	2 years ago
Roberto Ierusalimschy	d324a0ccf9	Simpler control for major collections	2 years ago
Roberto Ierusalimschy	ec61be9a7e	'l_mem' renamed to 'l_obj' to count objects	2 years ago
Roberto Ierusalimschy	f356d5acdd	First version of GC counting objects for control Still needs to review generational mode.	2 years ago
Roberto Ierusalimschy	76953316d1	Added a counter of the total number of existing objects It may simplify the control of the garbage collector.	2 years ago
Roberto Ierusalimschy	9ede317c70	Threads are created like other objects Using a version of 'luaC_newobj' that allows offsets (extra space before the object itself).	2 years ago
Roberto Ierusalimschy	413a393e62	Stack indices changed to union's That will allow to change pointers to offsets while reallocating the stack.	2 years ago
Roberto Ierusalimschy	1e64c1391f	Bug: stack overflow with nesting of coroutine.close	2 years ago
Roberto Ierusalimschy	0bfc572e51	Bug: GC is not reentrant As the GC is not reentrant, finalizers should not be able to invoke it.	3 years ago
Roberto Ierusalimschy	1de95e97ef	Bug: Lua stack still active when closing a state	3 years ago
Roberto Ierusalimschy	bfbff3703e	Bug: Wrong status in coroutine during reset When closing variables during 'coroutine.close' or 'lua_resetthread', the status of a coroutine must be set to LUA_OK; a coroutine should not run with any other status. (See assertion in 'lua_callk'.) After the reset, the status should be kept as normal, as any error was already reported.	3 years ago
Roberto Ierusalimschy	bef250eb8d	Details Comments and small improvements in the manual.	4 years ago
Roberto Ierusalimschy	1537d6680b	New control for reentrancy of emergency collections Instead of assuming that shrinking a block may be an emergency collection, use an explicit field ('gcstopem') to stop emergency collections while GC is working.	4 years ago
Roberto Ierusalimschy	59c88f846d	Broadening the use of branch hints More uses of macros 'likely'/'unlikely' (renamed to 'l_likely'/'l_unlikely'), both in range (extended to the libraries) and in scope (extended to hooks, stack growth).	4 years ago
Roberto Ierusalimschy	4e47f81188	New implementation for to-be-closed variables To-be-closed variables are linked in their own list, embedded into the stack elements. (Due to alignment, this information does not change the size of the stack elements in most architectures.) This new list does not produce garbage and avoids memory errors when creating tbc variables.	4 years ago
Roberto Ierusalimschy	c63e5d212b	New macro 'completestate'	4 years ago
Roberto Ierusalimschy	6ccd24eff5	Simpler handling of errors when creating tbc variables New field 'lua_State.ptbc' keeps to-be-closed variable until its upvalue is created, so that it can be closed in case of a memory-allocation error.	4 years ago
Roberto Ierusalimschy	b07fc10e91	Allow yields inside '__close' metamethods Initial implementation to allow yields inside '__close' metamethods. This current version still does not allow a '__close' metamethod to yield when called due to an error. '__close' metamethods from C functions also are not allowed to yield.	4 years ago
Roberto Ierusalimschy	6188f3a654	Reset thread before panicking Before panicking, it is simpler to reset the thread instead of closing its variables and adjust the top manually.	4 years ago
Roberto Ierusalimschy	7af27ef59d	Cleaner handling of errors in '__close' metamethods Instead of protecting each individual metamethod call, protect the entire call to 'luaF_close'.	4 years ago
Roberto Ierusalimschy	409256b784	'coroutine.close'/'lua_resetthread' report original errors Besides errors in closing methods, 'coroutine.close' and 'lua_resetthread' also consider the original error that stopped the thread, if any.	4 years ago
Roberto Ierusalimschy	65d2294454	Changed access to global table in the registry The global table is always in the array part of the registry; we can use this fact to make its access slightly more efficient.	4 years ago
Roberto Ierusalimschy	d282652561	Bug when growing a stack When a stack grows, its extra area can be in use, and it becomes part of the common area. So, the extra area must be kept correct all the times. (Bug introduced by commit 5aa36e894f5.)	4 years ago
Roberto Ierusalimschy	9a89fb1c9d	Hash always use all characters in a long string Hashes for long strings are computed only when they are used as keys in a table, not a too common case. And, in that case, it is to easy to force collisions changing only the characters which are not part of the hash.	4 years ago
Roberto Ierusalimschy	5aa36e894f	No more field 'lua_State.stacksize' The stack size is derived from 'stack_last', when needed. Moreover, the handling of stack sizes is more consistent, always excluding the extra space except when allocating/deallocating the array.	4 years ago
Roberto Ierusalimschy	490d42b5f8	Correct handling of 'luaV_execute' invocations The previous stackless implementations marked all 'luaV_execute' invocations as fresh. However, re-entering 'luaV_execute' when resuming a coroutine should not be a fresh invocation. (It works because 'unroll' called 'luaV_execute' for each call entry, but it was slower than letting 'luaV_execute' finish all non-fresh invocations.)	4 years ago
Roberto Ierusalimschy	287b302acb	Revision of stackless implementation - more organized handling of 'nCcalls' - comments - deprecation of 'setcstacklimit'	4 years ago
Roberto Ierusalimschy	5d8ce05b3f	Back to a stackless implementation A "with stack" implementation gains too little in performance to be worth all the noise from C-stack overflows. This commit is almost a sketch, to test performance. There are several pending stuff: - review control of C-stack overflow and error messages; - what to do with setcstacklimit; - review comments; - review unroll of Lua calls.	4 years ago
Roberto Ierusalimschy	0dc5deca1c	Optimization in 'markold' OLD1 objects can be potentially anywhere in the 'allgc' list (up to 'reallyold'), but frequently they are all after 'old1' (natural evolution of survivals) or do not exist at all (when all objects die young). So, instead of 'markold' starts looking for them always from the start of 'allgc', the collector keeps an extra pointer, 'firstold1', that points to the first OLD1 object in the 'allgc' list, or is NULL if there are no OLD1 objects in that list.	4 years ago
Roberto Ierusalimschy	b4c353434f	Details The fields 'old' and 'finobjold' were renamed 'old1' and 'finobjold1', respectively, to make clearer the main ages of their elements.	4 years ago
Roberto Ierusalimschy	a2195644d8	Fixed bug: invalid 'oldpc' when returning to a function The field 'L->oldpc' is not always updated when control returns to a function; an invalid value can seg. fault when computing 'changedline'. (One example is an error in a finalizer; control can return to 'luaV_execute' without executing 'luaD_poscall'.) Instead of trying to fix all possible corner cases, it seems safer to be resilient to invalid values for 'oldpc'. Valid but wrong values at most cause an extra call to a line hook.	4 years ago
Roberto Ierusalimschy	314c6057b7	Avoid any code before locks in the API For consistency in the C API, avoid any initializations before callling lua_lock.	4 years ago
Roberto Ierusalimschy	d39ea8b3ce	Make sure that main thread is non yieldable Main thread must be non yieldable even at "level 0" (bare API), outside the 'pcall' from 'lua.c'.	4 years ago

1 2 3 4 5 ...

365 Commits (3e88b72b8e71c0946d089a04876e7bdc61d187a9)