Before this commit, iclasses were "shady", or not protected by write
barriers. Because of that, the GC needs to spend more time marking these
objects than otherwise.
Applications that make heavy use of modules should see reduction in GC
time as they have a significant number of live iclasses on the heap.
Put logic for iclass method table ownership into a function
Remove calls to WB_UNPROTECT and insert write barriers for iclasses
This commit relies on the following invariant: for any non oirigin
iclass I, RCLASS_M_TBL(I) == RCLASS_M_TBL(RBasic(I)->klass). This
invariant did not hold prior to 98286e9 for classes and modules that
have prepended modules.
Added by alanwu (Alan Wu) almost 5 years ago
Remove write barrier exemption for T_ICLASS
Before this commit, iclasses were "shady", or not protected by write
barriers. Because of that, the GC needs to spend more time marking these
objects than otherwise.
Applications that make heavy use of modules should see reduction in GC
time as they have a significant number of live iclasses on the heap.
This commit relies on the following invariant: for any non oirigin
iclass
I,RCLASS_M_TBL(I) == RCLASS_M_TBL(RBasic(I)->klass). Thisinvariant did not hold prior to 98286e9 for classes and modules that
have prepended modules.
[Feature #16984]