[#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:60753] [ruby-trunk - Feature #9420] warn and puts should be atomic
From:
glass.saga@...
Date:
2014-02-15 05:46:38 UTC
List:
ruby-core #60753
Issue #9420 has been updated by Masaki Matsushita. Assignee set to Masaki Matsushita ---------------------------------------- Feature #9420: warn and puts should be atomic https://bugs.ruby-lang.org/issues/9420#change-45170 * Author: Eric Wong * Status: Open * Priority: Low * Assignee: Masaki Matsushita * Category: core * Target version: current: 2.2.0 ---------------------------------------- Since we added use of writev in r44618, we should make warn/puts atomic. It would make development of multiprocess/multithreaded processes easier, I think it was intended to be atomic based on old comments in io.c: ``` - /* - * xxx: use writev to avoid double write if available - * writev may help avoid context switch between "a" and "\n" in - * STDERR.puts "a" [ruby-dev:25080] (rebroken since native threads - * introduced in 1.9) - */ ``` -- http://bugs.ruby-lang.org/