[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60751] Re: volatile usages
From:
Eric Wong <normalperson@...>
Date:
2014-02-15 01:53:00 UTC
List:
ruby-core #60751
array.c: volatile in rb_ary_each along with the explanation in r32201 is scaring me :x If that volatile is needed, then it would also be necessary in similar functions such as rb_ary_each_with_index and rb_reverse_each. Of course, those functions do not use volatile and seem fine after all these years. Anways, with r32201, I can understand the need for volatile in cont.c because of setjmp. Also, vm_call_cfunc no longer uses volatile, but its use in rb_ary_each is troubling... Anyways, I cannot find problems with Debian clang version 3.0-6.2 (tags/RELEASE_30/final) (based on LLVM 3.0)