lua/testes, branch v5.4.3A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.32021-03-10T13:35:57+00:00File 'tracegc.lua' added to 'packtests'2021-03-10T13:35:57+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-10T13:35:57+00:00urn:sha1:05b13651f96117674ba30dace03620658760acbdlua_settop/lua_pop closes to-be-closed variables2021-03-09T14:42:45+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-09T14:42:45+00:00urn:sha1:511d53a826760dd11cd82947184583e2d094e2d2
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'2021-03-05T15:10:34+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-05T15:10:34+00:00urn:sha1:f5df7f91f70234850484d26caf24e71e001e5304
The assertion cannot compute 'f->abslineinfo[i]' when the initial
estimate 'i' is -1.
New test module 'tracegc'2021-03-01T16:54:29+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-03-01T16:54:29+00:00urn:sha1:5276973224066e591b0f1a79c3b091d395848ac4
New module easies the inclusion of GC tracing in individual test files.
New control for reentrancy of emergency collections2021-02-26T14:41:02+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-26T14:41:02+00:00urn:sha1:1537d6680bb66dc2484e11815bc2cd0e31ca39cc
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'2021-02-25T16:39:36+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-25T16:39:36+00:00urn:sha1:e0260eb2d4085723302d637dd8f3fca339d18817
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.)
Bug: 'string.concat' error message uses wrong format2021-02-15T16:31:45+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-15T16:31:45+00:00urn:sha1:c03c527fd207b4ad8f5a8e0f4f2c176bd227c979Bug: cannot allow the call 'debug.getinfo(0, ">")'2021-02-15T13:38:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-15T13:38:09+00:00urn:sha1:38cc7d40a4bcb89314d212fdffd2ca8deebc3cb7
A 'what' argument starting with '>' indicates that there is a function
in the C stack, which won't be there if the first argument is not a
function.
'__close' methods can yield in the return of a C function2021-02-12T16:36:30+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-12T16:36:30+00:00urn:sha1:bc970005ce2e258e29a5c315ea4e49f76a66586e
When, inside a coroutine, a C function with to-be-closed slots return,
the corresponding metamethods can yield. ('__close' metamethods called
through 'lua_closeslot' still cannot yield, as there is no continuation
to go when resuming.)
New implementation for to-be-closed variables2021-02-09T17:00:05+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-02-09T17:00:05+00:00urn:sha1:4e47f81188d37e29027158b76271d02a781242e2
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.