summaryrefslogtreecommitdiff
path: root/mjit_worker.c
diff options
context:
space:
mode:
authork0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-11-06 07:30:37 (GMT)
committerk0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-11-06 07:30:37 (GMT)
commit6c2014768eaee865fcd5ceabfbd6fcf4fed4b13c (patch)
treee81768095a55204a0f24d0c5828f5491676cd29a /mjit_worker.c
parente0a35586689bdd4fc8713496876bdfba6b73b43b (diff)
mjit_worker.c: don't use _one for now
I'm planning to use _one later, but it may be doubly registered by switching `stop_worker_p` now and so we should not use _one for now. Otherwise stale job may reject new job registration and copy_cache_from_main_thread may wait forever. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65571 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'mjit_worker.c')
-rw-r--r--mjit_worker.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/mjit_worker.c b/mjit_worker.c
index fd83e7a..6abd5f9 100644
--- a/mjit_worker.c
+++ b/mjit_worker.c
@@ -1145,7 +1145,7 @@ copy_cache_from_main_thread(struct mjit_copy_job *job)
return job->finish_p;
}
- if (!rb_postponed_job_register_one(0, mjit_copy_job_handler, (void *)job))
+ if (!rb_postponed_job_register(0, mjit_copy_job_handler, (void *)job))
return FALSE;
CRITICAL_SECTION_START(3, "in MJIT copy job wait");
/* checking `stop_worker_p` too because `RUBY_VM_CHECK_INTS(ec)` may not