summaryrefslogtreecommitdiff
path: root/mjit.c
diff options
context:
space:
mode:
authorKoichi Sasada <ko1@atdot.net>2021-01-04 18:08:25 +0900
committerNARUSE, Yui <naruse@airemix.jp>2021-01-13 17:06:16 +0900
commitb93e16dc0f45069d4a5fcce20d5c4437e151f0a8 (patch)
tree58e71dd4acd25b3deca641a6d5d2e25432dbc646 /mjit.c
parent95aff214687a5e12c3eb57d056665741e734c188 (diff)
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.c18
1 files changed, 0 insertions, 18 deletions
diff --git a/mjit.c b/mjit.c
index d87961d7cc..4a14fa7ae1 100644
--- a/mjit.c
+++ b/mjit.c
@@ -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)