lua/lstate.h, branch v5.4.9A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.4.92026-07-22T17:42:55+00:00Bug: GC checks stack space before running finalizer2026-07-22T17:42:55+00:00Roberto Iroberto@inf.puc-rio.br2026-07-22T17:42:55+00:00urn:sha1:8511e90b7df5daf139aba290b9c9c1595927e7b3
If some stack does not have a minimum available space, the GC defers
calling a finalizer until the next cycle. That avoids errors while
running a finalizer that the programmer cannot control.
Bug: Call hook may be called twice when count hook yields2023-07-25T19:50:44+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-07-25T19:50:44+00:00urn:sha1:1b3f507f620d996ffb69da7476a19251acfb89ca
Took the opportunity and moved the code that controls call hooks
in 'luaV_execute' into a function.
Several functions turned 'static'2023-05-22T17:47:54+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-05-22T17:47:54+00:00urn:sha1:9be74ccc214eb6f4d9d0b9496fd973542c7377d9
Several functions that were already being used only inside their
own file have been declared as 'static'.
Details in some header files2022-12-14T19:20:39+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-12-14T19:20:39+00:00urn:sha1:6aabf4b15e7637c2ab4133abf3df0a77f34b6005
Identifier LUA_NUMTAGS was deprecated (changed to LUA_NUMTYPES) +
better handling of some inclusion loops.
Stack indices changed to union's2022-10-29T15:06:37+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2022-10-29T15:06:37+00:00urn:sha1:413a393e6222482f46599e138bebac162610a572
That will allow to change pointers to offsets while reallocating
the stack.
Fix debug information about finalizers2021-12-14T15:50:05+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-12-14T15:50:05+00:00urn:sha1:066e0f93c4901e601d93e31fb700f8f66f95feb8
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.)
Bug: GC is not reentrant2021-12-13T13:41:17+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-12-13T13:41:17+00:00urn:sha1:0bfc572e51d9035a615ef6e9523f736c9ffa8e57
As the GC is not reentrant, finalizers should not be able to invoke it.
Bug: yielding in '__close' mess up number of returns2021-04-16T18:41:44+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2021-04-16T18:41:44+00:00urn:sha1:681297187ec45268e872b26753c441586c12bdd8
Yielding in a __close metamethod called when returning vararg results
changes the top and so messes up the number of returned values.
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.
'__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.)