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

Commit Graph

Author	SHA1	Message	Date
Roberto Ierusalimschy	ba089bcb08	Details Added comments in the makefile about other useful '-fsanitize' options.	2 years ago
Roberto Ierusalimschy	1e64c1391f	Bug: stack overflow with nesting of coroutine.close	2 years ago
Roberto Ierusalimschy	b85816b9a8	Removed test function 'luaH_isdummy' It was not being used anywhere.	2 years ago
Roberto Ierusalimschy	c954db3924	Option '-l g=mod' added to the manual Plus some other improvements in the manual.	2 years ago
Roberto Ierusalimschy	14d2803e55	Details Some cast operations rewritten to use respective macros.	2 years ago
Roberto Ierusalimschy	7f12bf40c4	Portability issue in a test for 'string.format'	2 years ago
Roberto Ierusalimschy	26be27459b	Negation in constant folding of '>>' may overflow	2 years ago
Roberto Ierusalimschy	cfbe378f90	Small simplification in overflow check in 'getfield' Subtracting a small non-negative int from a non-negative int cannot overflow, and adding a non-negative int to INT_MIN cannot overflow.	2 years ago
Roberto Ierusalimschy	a1089b415a	Bug: 'utf8.codes' accepts spurious continuation bytes	2 years ago
Roberto Ierusalimschy	f8c4c4fcf2	New test for table rehash	2 years ago
Roberto Ierusalimschy	71bc69c2af	Note in the manual about using '...' as an expression	2 years ago
Roberto Ierusalimschy	cd56f222b7	Corrected error message in 'table.remove'	2 years ago
Roberto Ierusalimschy	69b77b6fde	Changed the growth rate of string buffers The growth rate of string buffers was reduced from 2 to 1.5 (3/2). As string buffers start larger (256~1024 bytes), they don't need to grow that fast. Moreover, a lower rate allows multiplicative growth up to larger sizes (3/2 of the maximum). (After that, the growth becomes linear, which is mostly useless.)	2 years ago
Roberto Ierusalimschy	997f11f543	Bug: 'break' may not properly close variable in a 'for' loop Function 'leaveblock' was generating "break" label before removing variables from the closing block. If 'createlabel' created a 'close' instruction (which it did when matching a goto/break that exited the scope of an upvalue), that instruction would use the wrong level.	2 years ago
Roberto Ierusalimschy	02060b7a37	Simpler handling of Byte Order Mark (BOM)	2 years ago
Roberto Ierusalimschy	a1f77a234a	Bug: set correct pause when (re)entering gen. collection.	2 years ago
Roberto Ierusalimschy	c6cea857a4	Better documentation for 'multires' expressions Manual has a new section explaining multires expressions, lists of expressions, and adjustments. This commit also corrects some comments in the code.	2 years ago
Roberto Ierusalimschy	d61b0c6028	More checks and documentation for uses of EXTRA_STACK	2 years ago
Roberto Ierusalimschy	196bb94d66	Bug: 'lua_settop' may use an invalid pointer to stack	2 years ago
Roberto Ierusalimschy	603b2c64ad	'luaV_concat' can use invalidated pointer to stack Bug introduced in commit `42d40581`.	2 years ago
Roberto Ierusalimschy	4a00f61276	'lua_checkstack' doesn't need to check stack overflow 'luaD_growstack' already checks that. This commit also fixes an internal bug in 'luaD_growstack': a large 'n' could cause an arithmetic overflow when computing 'needed'.	2 years ago
Roberto Ierusalimschy	42d40581dd	Save stack space while handling errors Because error handling (luaG_errormsg) uses slots from EXTRA_STACK, and some errors can recur (e.g., string overflow while creating an error message in 'luaG_runerror', or a C-stack overflow before calling the message handler), the code should use stack slots with parsimony. This commit fixes the bug "Lua-stack overflow when C stack overflows while handling an error".	3 years ago
Roberto Ierusalimschy	e435aaabef	Details (identation and typos)	3 years ago
Roberto Ierusalimschy	315639d3bb	Factoring out common parts of 'codearith' and 'codebitwise'	3 years ago
Roberto Ierusalimschy	c764ca71a6	Bug: Wrong code generation in bitwise operations	3 years ago
Roberto Ierusalimschy	295cde9454	New release number (5.4.5)	3 years ago
Roberto Ierusalimschy	f3cfd5bf2b	Details Comments + manual + identation + asserts about stack limits that were not allowing the use of the full stack	3 years ago
Roberto Ierusalimschy	8426d9b4d4	Avoid computing invalid addresses luaV_execute should compute 'ra' only when the instruction uses it. Computing an illegal address is undefined behavior even if the address is never dereferenced.	3 years ago
Roberto Ierusalimschy	1f3c6f4534	Bug: Lua can generate wrong code when _ENV is <const>	3 years ago
Roberto Ierusalimschy	25b143dd34	Bug: lua.c assumes that argv has at least one element	3 years ago
Roberto Ierusalimschy	5d708c3f9c	Explanation of borders in the manual The explanation includes the limit case of maxinteger being a border. It also avoids the term "natural", which might include large floats with natural values.	3 years ago
Roberto Ierusalimschy	8dd2c912d2	Detail Warnings with clang when using long double for Lua floats.	3 years ago
Roberto Ierusalimschy	05ac2409ee	New year (2022)	3 years ago
Roberto Ierusalimschy	597a53bbc6	Bug: finalizer calling exit can corrupt finalization order 'os.exit' can call lua_close again, separating new finalizers created after all previous finalizers were already separated.	3 years ago
Roberto Ierusalimschy	86ec152433	Details correction in macro for hard tests + type in comment	3 years ago
Roberto Ierusalimschy	cf613cdc6f	Bug: finalizers can be called with an invalid stack The call to 'checkstackGC' can run finalizers, which will find an inconsistent CallInfo, as 'ci' is half updated at the point of call.	3 years ago
Roberto Ierusalimschy	066e0f93c4	Fix debug information about finalizers The flag CIST_FIN does not mark a finalizer, but the function that was running when the finalizer was called. (So, the function did not call the finalizer, but it looks that way in the stack.)	3 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	ad3942adba	Main 'mainposition' replaced by 'mainpositionTV' Handle values in table keys as the special cases they are, and not the other way around.	3 years ago
Roberto Ierusalimschy	48835c76c8	Wrong assert in 'collectvalidlines'	3 years ago
Roberto Ierusalimschy	6b3e116d44	Corrected bug in 'luaD_tryfuncTM' The pointer to the metamethod can be invalidated by a finalizer that can run during a GC in 'checkstackGCp'. (This commit also fixes a detail in the manual.) Bug introduced in commit `91673a8ec`.	3 years ago
Roberto Ierusalimschy	e8deac5a41	Avoid OP_VARARGPREP for active lines when building the table 'activelines' for a vararg function, this first instruction does not make the first line active.	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	74d99057a5	Bug: C stack overflow with coroutines 'coroutine.resume' did not increment counter of C calls when continuing execution after a protected error (that is, while running 'precover').	3 years ago
Roberto Ierusalimschy	1fce5bea81	More uniform implementation for tail calls 'luaD_pretailcall' mimics 'luaD_precall', handling call metamethods and calling C functions directly. That makes the code in the interpreter loop simpler. This commit also goes back to emulating the tail call in 'luaD_precall' with a goto, as C compilers may not do proper tail calls and the C stack can overflow much sooner than the Lua stack (which grows as the metamethod is added to it).	3 years ago
Roberto Ierusalimschy	3699446aaf	Removed goto's in 'luaD_precall' (plus a detail in lauxlib.h.)	3 years ago
Roberto Ierusalimschy	0e5071b5fb	Avoid taking the address of a 'TValue' field That structure can be packed in the future.	3 years ago
Roberto Ierusalimschy	87a9573b2e	Documentation Better explanation about the guaranties of multiple assignment in the manual.	3 years ago
Roberto Ierusalimschy	deac067ed3	Avoid overflows when incrementing parameters in C Any C function can receive maxinteger as an integer argument, and therefore cannot increment it without some care (e.g., doing unsigned arithmetic as the core does).	3 years ago

1 2 3 4 5 ...

5447 Commits (ba089bcb08a0efc6c26fb5c1e3c9d61c00cc012c) All Branches Search

5447 Commits (ba089bcb08a0efc6c26fb5c1e3c9d61c00cc012c)

All Branches