From ed590bdbfc5222d7658fee6a836d046ab17cd1b4 Mon Sep 17 00:00:00 2001 From: normal Date: Sun, 22 Apr 2018 12:09:07 +0000 Subject: thread*: all condvars are monotonic There's no reason to use CLOCK_REALTIME for any condvars in Ruby. Indeed, we initialized all condvars with RB_CONDATTR_CLOCK_MONOTONIC anyway; so simplify our code and reduce ifdefs. [ruby-core:85639] [Misc #14497] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63238 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- thread_win32.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'thread_win32.c') diff --git a/thread_win32.c b/thread_win32.c index 530f6e7cde..ab308905cb 100644 --- a/thread_win32.c +++ b/thread_win32.c @@ -508,7 +508,7 @@ native_cond_timeout(rb_nativethread_cond_t *cond, struct timespec timeout_rel) #endif void -rb_native_cond_initialize(rb_nativethread_cond_t *cond, int flags) +rb_native_cond_initialize(rb_nativethread_cond_t *cond) { cond->next = (struct cond_event_entry *)cond; cond->prev = (struct cond_event_entry *)cond; -- cgit v1.2.3