[#79440] [Ruby trunk Bug#13188] Reinitialize Ruby VM. — shyouhei@...
Issue #13188 has been updated by Shyouhei Urabe.
6 messages
2017/02/06
[#79441] Re: [Ruby trunk Bug#13188] Reinitialize Ruby VM.
— SASADA Koichi <ko1@...>
2017/02/06
On 2017/02/06 10:10, shyouhei@ruby-lang.org wrote:
[#79532] Immutable Strings vs Symbols — Daniel Ferreira <subtileos@...>
Hi,
15 messages
2017/02/15
[#79541] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/15
Em 15-02-2017 05:05, Daniel Ferreira escreveu:
[#79543] Re: Immutable Strings vs Symbols
— Daniel Ferreira <subtileos@...>
2017/02/16
Hi Rodrigo,
[#79560] Re: Immutable Strings vs Symbols
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2017/02/16
Em 15-02-2017 22:39, Daniel Ferreira escreveu:
[ruby-core:79474] Re: [Ruby trunk Bug#13188] Reinitialize Ruby VM.
From:
Eric Wong <normalperson@...>
Date:
2017-02-07 22:18:06 UTC
List:
ruby-core #79474
SASADA Koichi <ko1@atdot.net> wrote: > On 2017/02/06 10:10, shyouhei@ruby-lang.org wrote: > > VM-stored pointers > > More correctly, thread-local variables (on pthread). Was it function call overhead from pthread_getspecific? Did you try __thread? I think __thread was GCC-specific, but clang supports it, too; and we can fall back to existing pthread_getspecific for other compilers. I think something similar was introduced for C11, too, but we're still on C89... But yeah, having VM struct passed with every function call (like mrb_state in mruby) is probably most portable and fast. Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>