[#75687] [Ruby trunk Bug#12416] struct rb_id_table lacks mark function — shyouhei@...
Issue #12416 has been reported by Shyouhei Urabe.
3 messages
2016/05/23
[#75763] [Ruby trunk Feature#12435] Using connect_nonblock to open TCP connections in Net::HTTP#connect — mohamed.m.m.hafez@...
Issue #12435 has been reported by Mohamed Hafez.
3 messages
2016/05/28
[#75774] Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock — Mohamed Hafez <mohamed.m.m.hafez@...>
Hi all, every now and then in my production server, I'm
4 messages
2016/05/30
[#75775] Re: Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock
— Mohamed Hafez <mohamed.m.m.hafez@...>
2016/05/30
Or does MRI's OpenSSL::SSL::SSLSocket#connect_nonblock just return
[#75782] Important: Somewhat backwards-incompatible change (Fwd: [ruby-cvs:62388] duerst:r55225 (trunk): * string.c: Activate full Unicode case mapping for UTF-8) — Martin J. Dürst <duerst@...>
With the change below, I have activated full Unicode case mapping for
4 messages
2016/05/31
[ruby-core:75688] Re: [Ruby trunk Bug#12416] struct rb_id_table lacks mark function
From:
Eric Wong <normalperson@...>
Date:
2016-05-23 08:07:39 UTC
List:
ruby-core #75688
shyouhei@ruby-lang.org wrote: > Bug #12416: struct rb_id_table lacks mark function > https://bugs.ruby-lang.org/issues/12416 > The struct rb_id_table can hold arbitrary VALUE values. Can, but currently does not (AFAIK). > Now that this > struct is reachable form Ruby's object space, it must understand what GC > requests to it. Do you have plans to hold arbitrary VALUE objects? > +++ b/iseq.c > @@ -128,6 +128,7 @@ rb_iseq_mark(const rb_iseq_t *iseq) > RUBY_MARK_UNLESS_NULL(compile_data->mark_ary); > RUBY_MARK_UNLESS_NULL(compile_data->err_info); > RUBY_MARK_UNLESS_NULL(compile_data->catch_table_ary); > + rb_id_table_mark(compile_data->ivar_cache_table); Right now, ivar_cache_table only holds Fixnum which does not need marking. Even with generational GC, I still prefer we not waste CPU cycles walking through tables for noops. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>