[#69084] [Ruby trunk - Feature #11124] [Open] [PATCH] lib/*: use monotonic clock for timeouts — normalperson@...
Issue #11124 has been reported by Eric Wong.
5 messages
2015/05/06
[#69138] [Ruby trunk - Feature #11136] [PATCH] webrick: avoid fcntl module — nobu@...
Issue #11136 has been updated by Nobuyoshi Nakada.
3 messages
2015/05/12
[#69160] [Ruby trunk - Feature #11146] [PATCH] variable.c: initialize generic_iv_tbl at start — nobu@...
Issue #11146 has been updated by Nobuyoshi Nakada.
4 messages
2015/05/13
[#69175] Re: [Ruby trunk - Feature #11146] [PATCH] variable.c: initialize generic_iv_tbl at start
— Eric Wong <normalperson@...>
2015/05/13
nobu@ruby-lang.org wrote:
[ruby-core:69371] [Ruby trunk - Bug #11185] [Open] [PATCH] openssl: use RB_GC_GUARD instead of volatile
From:
normalperson@...
Date:
2015-05-27 00:50:32 UTC
List:
ruby-core #69371
Issue #11185 has been reported by Eric Wong. ---------------------------------------- Bug #11185: [PATCH] openssl: use RB_GC_GUARD instead of volatile https://bugs.ruby-lang.org/issues/11185 * Author: Eric Wong * Status: Open * Priority: Normal * Assignee: Eric Wong * ruby -v: * Backport: 2.0.0: REQUIRED, 2.1: REQUIRED, 2.2: REQUIRED ---------------------------------------- From doc/extension.rdoc: > > Using the RB_GC_GUARD macro is preferable to using the "volatile" > keyword in C. RB_GC_GUARD has the following advantages: > > 1) the intent of the macro use is clear > > 2) RB_GC_GUARD only affects its call site, "volatile" generates some > extra code every time the variable is used, hurting optimization. > > 3) "volatile" implementations may be buggy/inconsistent in some > compilers and architectures. RB_GC_GUARD is customizable for broken > systems/compilers without those without negatively affecting other > systems. ---Files-------------------------------- 0001-openssl-use-RB_GC_GUARD-instead-of-volatile.patch (2.5 KB) -- https://bugs.ruby-lang.org/