lua/lgc.c, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12026-04-23T21:00:23+00:00new macro 'setnilvalue2s'2026-04-23T21:00:23+00:00Roberto Iroberto@inf.puc-rio.br2026-04-23T21:00:23+00:00urn:sha1:ae23e726018bd31a25c1279600328d90207ec81cMore effort in avoiding errors in finalizers2026-01-11T18:36:03+00:00Roberto Iroberto@inf.puc-rio.br2026-01-11T18:36:03+00:00urn:sha1:2a7cf4f319fc276f4554a8f6364e6b1ba4eb2ded
Before calling a finalizer, Lua not only checks stack limits, but
actually ensures that a minimum number of slots are already allocated
for the call. (If it cannot ensure that, it postpones the finalizer.)
That avoids finalizers not running due to memory errors that the
programmer cannot control.
Details2025-12-23T17:44:06+00:00Roberto Iroberto@inf.puc-rio.br2025-12-23T17:44:06+00:00urn:sha1:578ae5745cecee56d48795cd4ae1eaf13618715c
typo in comment + formatting + logical 'and' was written as a bitwise
operation (makes code more fragile)
GC checks stack space before running finalizer2025-12-13T19:16:59+00:00Roberto Iroberto@inf.puc-rio.br2025-12-13T19:16:59+00:00urn:sha1:a5522f06d2679b8f18534fd6a9968f7eb539dc31
If the stack does not have some 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.
External strings are as good as internal ones2025-11-11T17:40:30+00:00Roberto Iroberto@inf.puc-rio.br2025-11-11T17:40:30+00:00urn:sha1:5b7d9987642f72d44223a8e5e79e013bb2b3d579
A '__mode' metafield and an "n" key both can be external strings.
Added some casts for 32-bit machines2025-07-29T14:50:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-07-29T14:50:20+00:00urn:sha1:c33bb08ffe04f24e09571b59eed3c9b59b622d91
When both 'int' and 'l_obj' have 32 bits, an unsigned int needs a
cast to be assigned to 'l_obj'. (As long as 'l_obj' can count the
total memory used by the system, these casts should be safe.)
New metatable in an all-weak table can fool the GC2025-06-16T19:29:32+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-16T19:29:32+00:00urn:sha1:9386e49a3173b68e8b5a7ba882c4c2faf557b61e
All-weak tables are not being revisited after being visited during
propagation; if it gets a new metatable after that, the new metatable
may not be marked.
Simpler code for 'traversetable'2025-06-16T18:50:12+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-06-16T18:50:12+00:00urn:sha1:8cd7ae7da06f54b97f95d6994d6bf47086e4e7eb
Check the mode in a separate function (getmode), instead of using
comma expressions inside the 'if' condition.
Details (typos in comments)2025-04-23T14:36:09+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-04-23T14:36:09+00:00urn:sha1:9b014d4bcd4ebadb523f1c1a1d38148d8526e5edIn gen. GC, some gray objects stay in gray lists2025-04-15T20:00:30+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-04-15T20:00:30+00:00urn:sha1:3dbb1a4b894c0744a331d4319d8d1704dc4ad943
In generational collection, objects marked as touched1 stay in gray
lists between collections. This commit fixes a bug introduced in
commit 808976bb59.