Searched refs:stop_worker_p (Results 1 – 3 of 3) sorted by relevance
29 if (stop_worker_p) { /* check if mutex is still alive, before calling CRITICAL_SECTION_START. */ in mjit_copy_job_handler()585 stop_worker_p = FALSE; in start_worker()683 …stop_worker_p = TRUE; /* Setting this inside loop because RUBY_VM_CHECK_INTS may make this FALSE. … in stop_worker()
206 static int stop_worker_p; variable1167 while (!job->finish_p && !stop_worker_p) { in copy_cache_from_main_thread()1199 while (!stop_worker_p) { in mjit_worker()1204 …st_empty(&unit_queue.head) || active_units.length >= mjit_opts.max_cache_size) && !stop_worker_p) { in mjit_worker()
6692 1. MJIT worker: dequeue ISeq (stop_worker_p was still FALSE)6694 sets `stop_worker_p = TRUE`, and fires RUBY_VM_CHECK_INTS() once6695 3. MJIT worker: register copy job, but found stop_worker_p is TRUE.8381 start_worker() which sets `stop_worker_p = FALSE` and it could wait for8382 MJIT worker stop forever even while `stop_worker_p` is FALSE.9978 switching `stop_worker_p` now and so we should not use _one for now.11792 Given that `copy_cache_from_main_thread()` breaks the loop when `stop_worker_p`11793 is TRUE, memory of `job` allocated by `alloca` may be invalid if `stop_worker_p`11797 stop checking `stop_worker_p`.