lua/testes/gengc.lua, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12025-08-09T18:08:53+00:00Details2025-08-09T18:08:53+00:00Roberto Iroberto@inf.puc-rio.br2025-08-09T18:08:53+00:00urn:sha1:5b179eaf6a78af5f000d76147af94669d04487b2Removed copyright notice from 'testes/all.lua'2025-03-12T17:00:58+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2025-03-12T17:00:58+00:00urn:sha1:ab66652b3270b95222dea134b5e47bb3afc434cc
All test files refer to the main copyright notice in 'lua.h'.
New mechanism to query GC parameters2024-01-16T20:02:55+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2024-01-16T20:02:55+00:00urn:sha1:4a8e48086433ad12f2991c07f3064278714fd0f1Removed compatibility option LUA_COMPAT_GCPARAMS2023-12-22T17:57:43+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-12-22T17:57:43+00:00urn:sha1:e81f586001d767c8de9b760ae2e2c3b5da1542c6
The meaning of different GC parameters changed, so there is point in
supporting old values for them. The new code simply ignores the
parameters when changing the GC mode, so the incompatibility is small.
New option "setparms" for 'collectgarbage'2023-12-22T17:48:07+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-12-22T17:48:07+00:00urn:sha1:e2cc179454c6aa6cde5f98954bd3783e0d5d53a3
The generational mode also uses the parameters for the incremental
mode in its major collections, so it should be easy to change those
parameters without having to change the GC mode.
Option 0 for step multiplier makes GC non-incremental2023-12-20T14:06:27+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2023-12-20T14:06:27+00:00urn:sha1:666e95a66d1a2ceb98bdf320980b3f655264a9c9TOUCHED2 objects are not always black2020-08-13T17:31:27+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-08-13T17:31:27+00:00urn:sha1:f7ce7e5faae69fcab0126d8bfd34b685f1dcb019
This commit fixes a bug introduced in commit 9cf3299fa. TOUCHED2
objects are always black while the mutator runs, but they can become
temporarily gray inside a minor collection (e.g., if the object is a
weak table).
Optimization in 'markold'2020-07-29T20:05:47+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-29T20:05:47+00:00urn:sha1:0dc5deca1c0182a4a3db2fcfd7bc721f27fb352b
OLD1 objects can be potentially anywhere in the 'allgc' list (up
to 'reallyold'), but frequently they are all after 'old1' (natural
evolution of survivals) or do not exist at all (when all objects die
young). So, instead of 'markold' starts looking for them always
from the start of 'allgc', the collector keeps an extra pointer,
'firstold1', that points to the first OLD1 object in the 'allgc' list,
or is NULL if there are no OLD1 objects in that list.
Fixed bug: barriers cannot be active during sweep2020-07-27T13:26:20+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-27T13:26:20+00:00urn:sha1:a6da1472c0c5e05ff249325f979531ad51533110
Barriers cannot be active during sweep, even in generational mode.
(Although gen. mode is not incremental, it can hit a barrier when
deleting a thread and closing its upvalues.) The colors of objects are
being changed during sweep and, therefore, cannot be trusted.
Added test for fix 127e7a6c8942020-07-13T16:37:01+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2020-07-13T16:37:01+00:00urn:sha1:0f1cd0eba99ea6d383e75b9ae488d00ad541c210