diff options
author | Koichi Sasada <ko1@atdot.net> | 2021-01-04 18:08:25 +0900 |
---|---|---|
committer | Koichi Sasada <ko1@atdot.net> | 2021-01-05 02:27:58 +0900 |
commit | e7fc353f044f9280222ca41b029b1368d2bf2fe3 (patch) | |
tree | 3e3a8e464dbc3767d5b71f17675d3f0dba6ac43f /mjit.c | |
parent | bf21faec1521540f2be05df400c37600b4316a0f (diff) | |
download | ruby-e7fc353f044f9280222ca41b029b1368d2bf2fe3.tar.gz |
enable constant cache on ractors
constant cache `IC` is accessed by non-atomic manner and there are
thread-safety issues, so Ruby 3.0 disables to use const cache on
non-main ractors.
This patch enables it by introducing `imemo_constcache` and allocates
it by every re-fill of const cache like `imemo_callcache`.
[Bug #17510]
Now `IC` only has one entry `IC::entry` and it points to
`iseq_inline_constant_cache_entry`, managed by T_IMEMO object.
`IC` is atomic data structure so `rb_mjit_before_vm_ic_update()` and
`rb_mjit_after_vm_ic_update()` is not needed.
Diffstat (limited to 'mjit.c')
-rw-r--r-- | mjit.c | 18 |
1 files changed, 0 insertions, 18 deletions
@@ -82,24 +82,6 @@ mjit_gc_exit_hook(void) CRITICAL_SECTION_FINISH(4, "mjit_gc_exit_hook"); } -// Lock setinlinecache -void -rb_mjit_before_vm_ic_update(void) -{ - if (!mjit_enabled) - return; - CRITICAL_SECTION_START(3, "before vm_ic_update"); -} - -// Unlock setinlinecache -void -rb_mjit_after_vm_ic_update(void) -{ - if (!mjit_enabled) - return; - CRITICAL_SECTION_FINISH(3, "after vm_ic_update"); -} - // Deal with ISeq movement from compactor void mjit_update_references(const rb_iseq_t *iseq) |