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

Commit Graph

Author	SHA1	Message	Date
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	84e32ad2eb	Added opcodes for arithmetic with K operands Added opcodes for all seven arithmetic operators with K operands (that is, operands that are numbers in the array of constants of the function). They cover the cases of constant float operands (e.g., 'x + .0.0', 'x^0.5') and large integer operands (e.g., 'x % 10000').	6 years ago
Roberto Ierusalimschy	35296e1fde	Details comments and other janitorial work.	6 years ago
Roberto Ierusalimschy	7f6f70853c	To-be-closed variable in 'for' loop separated from the state The variable to be closed in a generic 'for' loop now is the 4th value produced in the loop initialization, instead of being the loop state (the 2nd value produced). That allows a loop to use a state with a '__toclose' metamethod but do not close it. (As an example, 'f:lines()' might use the file 'f' as a state for the loop, but it should not close the file when the loop ends.)	6 years ago
Roberto Ierusalimschy	5e76a4fd31	New macros for arithmetic/bitwise operations in 'luaV_execute' The repetitive code of the arithmetic and bitwise operators in the main iterpreter loop was moved to appropriate macros. (As a detail, the function 'luaV_div' was renamed 'luaV_idiv', as it does an "integer division" (floor division).	6 years ago
Roberto Ierusalimschy	e8c779736f	Removed internal cache for closures The mechanism of "caching the last closure created for a prototype to try to reuse it the next time a closure for that prototype is created" was removed. There are several reasons: - It is hard to find a natural example where this cache has a measurable impact on performance. - Programmers already perceive closure creation as something slow, so they tend to avoid it inside hot paths. (Any case where the cache could reuse a closure can be rewritten predefining the closure in some variable and using that variable.) - The implementation was somewhat complex, due to a bad interaction with the generational collector. (Typically, new closures are new, while prototypes are old. So, the cache breaks the invariant that old objects should not point to new ones.)	6 years ago
Roberto Ierusalimschy	947a372f58	State in generic 'for' acts as a to-be-closed variable The implicit variable 'state' in a generic 'for' is marked as a to-be-closed variable, so that the state will be closed as soon as the loop ends, no matter how. Taking advantage of this new facility, the call 'io.lines(filename)' now returns the open file as a second result. Therefore, an iteraction like 'for l in io.lines(name)...' will close the file even when the loop ends with a break or an error.	6 years ago
Roberto Ierusalimschy	e073cbc2e5	Better error messages for invalid operands in numeric 'for' "Better" and similar to error messages for invalid function arguments. old message: 'for' limit must be a number new message: bad 'for' limit (number expected, got table)	6 years ago
Roberto Ierusalimschy	6e9b719694	More uniformity in code generation for 'for' loops Added new instruction 'OP_TFORPREP' to prepare a generic for loop. Currently it is equivalent to a jump (but with a format 'iABx', similar to other for-loop preparing instructions), but soon it will be the place to create upvalues for closing loop states.	6 years ago
Roberto Ierusalimschy	41c800b352	Closing methods should not interfere with returning values A closing method cannot be called in its own stack slot, as there may be returning values in the stack after that slot, and the call would corrupt those values. Instead, the closing method must be copied to the top of the stack to be called. Moreover, even when a function returns no value, its return istruction still has to have its position (which will set the stack top) after the local variables, otherwise a closing method might corrupt another not-yet-called closing method.	6 years ago
Roberto Ierusalimschy	3c7dc52909	Handling of memory errors when creating to-be-closed upvalues	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	5382a22e0e	Corrections in the implementation of '%' for floats. The multiplication (m*b) used to test whether 'm' is non-zero and 'm' and 'b' have different signs can underflow for very small numbers, giving a wrong result. The use of explicit comparisons solves this problem. This commit also adds several new tests for '%' (both for floats and for integers) to exercise more corner cases, such as very large and very small values.	6 years ago
Roberto Ierusalimschy	8c8a91f2ef	Deprecated the emulation of '__le' using '__lt' As hinted in the manual for Lua 5.3, the emulation of the metamethod for '__le' using '__le' has been deprecated. It is slow, complicates the logic, and it is easy to avoid this emulation by defining a proper '__le' function. Moreover, often this emulation was used wrongly, with a programmer assuming that an order is total when it is not (e.g., NaN in floating-point numbers).	6 years ago
Roberto Ierusalimschy	3dcd04ad61	details Minor optimizations in 'lvm.c'. (Not exactly optimizations, but more chances for optimizations.)	6 years ago
Roberto Ierusalimschy	06e08c6d05	Fixed bug in OP_IDIVI Opocode was using 'luai_numdiv' (float division) instead of 'luai_numidiv' (integer division).	6 years ago
Roberto Ierusalimschy	a314409dba	in generational mode, an emergency collection can turn any object black during any memory allocation + 'luaT_getvarargs' may reallocate the stack, and therefore the top must be correct.	6 years ago
Roberto Ierusalimschy	6e600695f8	field 'sizearray' in struct 'Table' changed to 'alimit', which can be used as a hint for '#t'	6 years ago
Roberto Ierusalimschy	fb8fa66136	no more 'luaH_emptyobject' and comparisons of addresses of global variables (instead, use a different kind of nil to signal the fake entry returned when a key is not found in a table)	7 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	e64e20ac81	minimizing the code ran by 'vmfetch' + no more 'vra' (the code is simpler without 'vra' and conversion is a no-op)	7 years ago
Roberto Ierusalimschy	03c6a05ec8	no more nil-in-table	7 years ago
Roberto Ierusalimschy	3d0b5edfe4	using unsigned comparison in 'l_intfitsf' (avoids one comparison)	7 years ago
Roberto Ierusalimschy	7b0b6b3b39	cannot use 'defined' inside a macro + call to 'luaT_keydef' must be protected	7 years ago
Roberto Ierusalimschy	4a1612ff9b	new experimental syntax using reserved word 'undef'	7 years ago
Roberto Ierusalimschy	62a392ff46	using jump tables when available	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	9243c414d9	first version of empty entries in tables (so that, in the future, tables can contain regular nil entries)	7 years ago
Roberto Ierusalimschy	c72ac048b9	conditional jumps "deunified" (if a jump table is used, the unification may harm jump prediction.)	7 years ago
Roberto Ierusalimschy	212095a601	new opcodes OP_GTI/OP_GEI	7 years ago
Roberto Ierusalimschy	06865aa01d	simpler implementation for 'LTintfloat'/'LEintfloat' + 'LTfloatint'/'LEfloatint'	7 years ago
Roberto Ierusalimschy	465b474899	small reorganization of 'luaV_flttointeger'/'luaV_tointeger'	7 years ago
Roberto Ierusalimschy	1afd5a152d	more generic way to handle 'gclist'	7 years ago
Roberto Ierusalimschy	49dae52d08	correct way to check stack space for vararg functions	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	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	5bd8d388de	OP_CONCAT does not move its result (to simplify its execution)	7 years ago
Roberto Ierusalimschy	d2fb34ac88	'OP_TAILCALL' calling C functions finishes the call and returns (instead of waiting for following 'OP_RETURN')	7 years ago
Roberto Ierusalimschy	ab0a851db4	'luaD_tryfuncTM' can ensure it does not change the stack	7 years ago
Roberto Ierusalimschy	ad960095bf	avoid jumping into a variable scope (C++ does not allow that)	7 years ago
Roberto Ierusalimschy	a9295a2b8e	typos in comments	7 years ago
Roberto Ierusalimschy	cf7eff45f3	keep control of stack top in Lua functions concentrated in 'luaV_execute'	7 years ago
Roberto Ierusalimschy	4676f6599e	new macros 'isOT'/'isIT' (plus exchanged parameters of OP_VARARG to make it similar to other 'isOT' instructions)	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	3153a41e33	no need to save 'pc' in case of allocation errors (allocation errors do not call message handlers)	7 years ago

1 2 3 4 5 ...

667 Commits (7696c6474fe51ed59fee324e78c1233af74febdd)