aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Avoid OP_VARARGPREP for active linesRoberto Ierusalimschy2021-11-102-1/+51
| | | | | when building the table 'activelines' for a vararg function, this first instruction does not make the first line active.
* Bug: Wrong status in coroutine during resetRoberto Ierusalimschy2021-11-083-5/+47
| | | | | | | | | 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.
* Bug: C stack overflow with coroutinesRoberto Ierusalimschy2021-11-032-2/+18
| | | | | | 'coroutine.resume' did not increment counter of C calls when continuing execution after a protected error (that is, while running 'precover').
* More uniform implementation for tail callsRoberto Ierusalimschy2021-10-293-44/+58
| | | | | | | | | | | '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).
* Removed goto's in 'luaD_precall'Roberto Ierusalimschy2021-10-182-25/+28
| | | | (plus a detail in lauxlib.h.)
* Avoid taking the address of a 'TValue' fieldRoberto Ierusalimschy2021-10-112-10/+10
| | | | That structure can be packed in the future.
* DocumentationRoberto Ierusalimschy2021-10-114-5/+13
| | | | | Better explanation about the guaranties of multiple assignment in the manual.
* Avoid overflows when incrementing parameters in CRoberto Ierusalimschy2021-09-226-9/+39
| | | | | | 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).
* Using 'inline' in some functionsRoberto Ierusalimschy2021-09-155-15/+32
| | | | | According to ISO C, "making a function an inline function suggests that calls to the function be as fast as possible." (Not available in C89.)
* Revamp of format validation in 'string.format'Roberto Ierusalimschy2021-09-033-36/+118
| | | | | When calling 'sprintf', not all conversion specifiers accept all flags; some combinations are undefined behavior.
* 'luaD_tryfuncTM' checks stack space by itselfRoberto Ierusalimschy2021-08-183-9/+11
|
* Undo simplification of tail calls (commit 901d760)Roberto Ierusalimschy2021-08-183-51/+51
| | | | Not that simpler and slower.
* Detail in 'testes/math.lua'Roberto Ierusalimschy2021-08-181-0/+1
| | | | Added a print with the random seeds used in the tests of 'random'.
* Option '-l' can give a name for the global variable.Roberto Ierusalimschy2021-08-162-15/+27
| | | | Sintax for this option now is '-l [globname=]modname'.
* Added tests for string reuse by the scannerRoberto Ierusalimschy2021-08-112-1/+25
|
* Improved documentation for 'lua_getinfo'Roberto Ierusalimschy2021-08-111-18/+24
|
* Bug: luaL_tolstring may get confused with negative indexRoberto Ierusalimschy2021-07-223-0/+20
| | | | | When object has a '__name' metafield, 'luaL_tolstring' used the received index after pushing a string on the stack.
* Bug: Negation in 'luaV_shiftr' may overflowRoberto Ierusalimschy2021-07-222-1/+6
| | | | Negation of an unchecked lua_Integer overflows with mininteger.
* Correction on documentation of string-buffer operationsRoberto Ierusalimschy2021-07-211-4/+4
| | | | | | All string-buffer operations can potentially change the stack in unspecified ways; the push/pop documentation in the manual should reflect that.
* Simplification in the parameters of 'luaD_precall'Roberto Ierusalimschy2021-06-303-14/+24
| | | | | | The parameters 'nresults' and 'delta1', in 'luaD_precall', were never meaningful simultaneously. So, they were combined in a single parameter 'retdel'.
* Bug: 'local function' can assign to '<const>' variablesRoberto Ierusalimschy2021-06-202-0/+3
|
* C functions can be tail called, tooRoberto Ierusalimschy2021-06-144-29/+29
| | | | | A tail call to a C function can have the behavior of a "real" tail call, reusing the stack frame of the caller.
* Simpler implementation for tail callsRoberto Ierusalimschy2021-06-113-39/+33
| | | | | Tail calls handled by 'luaD_precall', like regular calls, to avoid code duplication.
* Avoid the term "undefined behavior" in the manualRoberto Ierusalimschy2021-06-091-3/+2
|
* 'index2value' more robustRoberto Ierusalimschy2021-05-241-5/+13
| | | | | 'index2value' accepts pseudo-indices also when called from a Lua function, through a hook.
* DetailsRoberto Ierusalimschy2021-05-242-14/+7
| | | | | - Removed unused (and trivial) definition LUA_UNSIGNEDBITS - Alignment structure in pack/unpack moved to a narrower scope
* Bug: yielding in '__close' mess up number of returnsRoberto Ierusalimschy2021-04-163-2/+71
| | | | | Yielding in a __close metamethod called when returning vararg results changes the top and so messes up the number of returned values.
* Align error messages for calling non-callable valuesRoberto Ierusalimschy2021-04-121-11/+37
| | | | | 'pcall(foo)' message was "attempt to call a table value", while 'pcall(function () foo() end) message was "global 'foo' is not callable".
* Bug: Lua source should not use C99 comments ("//")Roberto Ierusalimschy2021-04-101-2/+4
|
* Bug: tbc variables in "for" loops don't avoid tail callsRoberto Ierusalimschy2021-04-072-6/+38
|
* Changes in cache for function constantsRoberto Ierusalimschy2021-03-302-8/+40
| | | | | | | | In 'lcode.c', when adding constants to the list of constants of a function, integers represent themselves in the cache and floats with integral values get a small delta to avoid collision with integers. (This change avoids creating artificial addresses; the old implementation converted integers to pointers to index the cache.)
* New hash function for integer keysRoberto Ierusalimschy2021-03-291-2/+14
| | | | | | | When integer keys do not form a sequence, it is better to use all their bits to compute their hashes. (The previous implementation was quite bad for integer keys with common lower bits, and disastrous for integer keys changing only in their upper 32 bits.)
* Allow yields inside '__pairs'Roberto Ierusalimschy2021-03-292-1/+27
|
* DetailsRoberto Ierusalimschy2021-03-295-16/+32
| | | | Comments and small improvements in the manual.
* Next release number (5.4.4)Roberto Ierusalimschy2021-03-291-2/+2
|
* Added option LUA_NOBUILTINv5.4.3Roberto Ierusalimschy2021-03-121-2/+4
| | | | | This option allows external code to avoid the use of gcc builtin macro '__builtin_expect' in the Lua API.
* DetailsRoberto Ierusalimschy2021-03-121-21/+40
| | | | Comments and order of hashing macros in 'ltable.c'.
* File 'tracegc.lua' added to 'packtests'Roberto Ierusalimschy2021-03-101-0/+1
|
* New implementation for 'tbclist'Roberto Ierusalimschy2021-03-102-13/+32
| | | | | | | | | | | | | | - Fixes a bug, by removing dummy nodes together with the node itself. (The previous implementation could leave dummy nodes in frames which otherwise had no tbc variables, and therefore would not close variables; that could leave 'tbclist' pointing higher than 'top', which could dangle if the stack shrank.) - Computes MAXDELTA based on the type of delta, to ease changing its type if needed. - Instead of 'isdummy', uses 'delta==0' to signal dummy nodes. (Dummy nodes always have MAXDELTA for their real delta.)
* Uses of "likely" in macros active to all usersRoberto Ierusalimschy2021-03-092-12/+15
| | | | | | | The use of 'l_likely' in auxlib macros 'luaL_argcheck' and 'luaL_argexpected' should not be restricted to Lua's own code. For that, 'l_likely' was renamed to 'luai_likely' to be exported to external code.
* lua_settop/lua_pop closes to-be-closed variablesRoberto Ierusalimschy2021-03-093-20/+44
| | | | | | The existence of 'lua_closeslot' is no reason for lua_pop not to close to-be-closed variables too. It is too error-prone for lua_pop not to close tbc variables being popped from the stack.
* Wrong assertion in 'getbaseline'Roberto Ierusalimschy2021-03-052-1/+12
| | | | | The assertion cannot compute 'f->abslineinfo[i]' when the initial estimate 'i' is -1.
* New release number (5.4.3)Roberto Ierusalimschy2021-03-032-4/+4
|
* Normalization of metamethod typography in the manualRoberto Ierusalimschy2021-03-021-10/+10
|
* Added assertions for proper use of string buffersRoberto Ierusalimschy2021-03-021-5/+17
|
* Stack check in warning function for testsRoberto Ierusalimschy2021-03-021-0/+2
| | | | | | The warning function using for tests need to check the stack before pushing anything. (Warning functions are not expected to access a Lua state, therefore they have no preallocated stack space.)
* New test module 'tracegc'Roberto Ierusalimschy2021-03-014-18/+54
| | | | New module easies the inclusion of GC tracing in individual test files.
* Stack reallocation done in two phasesRoberto Ierusalimschy2021-02-271-7/+21
| | | | | | | | | $he stack reallocation is done in two steps (allocation + free) because the correction of the pointers pointing into the stack must be done while both addresses (the old stack and the new one) are valid. In ISO C, any pointer use after the pointer has been deallocated is undefined behavior. The compiler option '-fsanitize=pointer-subtract' (plus what it needs to work) complained about the old implementation.
* New control for reentrancy of emergency collectionsRoberto Ierusalimschy2021-02-265-25/+46
| | | | | | 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.
* Bug (kind of) in 'isinstack'Roberto Ierusalimschy2021-02-252-6/+17
| | | | | | | The function 'isinstack' tried to work around the undefined behavior of subtracting two pointers that do not point to the same object, but the compiler killed to trick. (It optimizes out the safety check, because in a correct execution it will be always true.)