commit | b9b554e0f68726b19274209ea6ce910b7e9f5fbf | [log] [tgz] |
---|---|---|
author | Roberto Ierusalimschy <roberto@inf.puc-rio.br> | Mon Aug 03 13:22:57 2020 -0300 |
committer | Roberto Ierusalimschy <roberto@inf.puc-rio.br> | Mon Aug 03 13:22:57 2020 -0300 |
tree | 5e0b126da4447bcb7bdfc80821d209dc86584a9e | |
parent | 0dc5deca1c0182a4a3db2fcfd7bc721f27fb352b [diff] |
Clearer handling of gray lists when entering generational mode When entering generational mode, all objects are old. So, the only objects that need to be in a gray list are threads, which can be assigned without barriers. Changes in anything else (e.g., weak tables) will trigger barriers that, if needed, will add the object to a gray list.