summaryrefslogtreecommitdiff
path: root/mjit.h
diff options
context:
space:
mode:
authork0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-03-17 02:00:30 (GMT)
committerk0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-03-17 02:00:30 (GMT)
commitc91c62b674736fd807a201b4314a48f854f1c2c0 (patch)
treea514ffb661c5ae2767c4df6c73e69ab729fbe942 /mjit.h
parent6cd5db8904379eeb3f80998814e028b6f1adc6a8 (diff)
mjit.c: add timeout for --jit-wait
Sometimes test hangs in `mjit_get_iseq_func` like this: http://ci.rvm.jp/results/trunk-test@ruby-sky3/659391 It seems that a process waiting in `mjit_get_iseq_func` does no longer have MJIT worker thread. We don't wait for JIT finish forever. So I added timeout for the case. I'm not sure why there was no MJIT worker thread in ruby-sky3 test process though. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62785 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'mjit.h')
-rw-r--r--mjit.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/mjit.h b/mjit.h
index 9bf2a00..c52b253 100644
--- a/mjit.h
+++ b/mjit.h
@@ -56,7 +56,7 @@ extern struct mjit_options mjit_opts;
extern int mjit_init_p;
extern void mjit_add_iseq_to_process(const rb_iseq_t *iseq);
-extern mjit_func_t mjit_get_iseq_func(const struct rb_iseq_constant_body *body);
+extern mjit_func_t mjit_get_iseq_func(struct rb_iseq_constant_body *body);
RUBY_SYMBOL_EXPORT_END
extern int mjit_compile(FILE *f, const struct rb_iseq_constant_body *body, const char *funcname);