[#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:60859] [ruby-trunk - Bug #9276] [Closed] "RUBY_FREE_MIN is obsolete. Use RUBY_GC_HEAP_FREE_SLOTS instead" warning should not be issued when both ENV vars are set.
From:
naruse@...
Date:
2014-02-19 06:25:01 UTC
List:
ruby-core #60859
Issue #9276 has been updated by Yui NARUSE. Status changed from Assigned to Closed ---------------------------------------- Bug #9276: "RUBY_FREE_MIN is obsolete. Use RUBY_GC_HEAP_FREE_SLOTS instead" warning should not be issued when both ENV vars are set. https://bugs.ruby-lang.org/issues/9276#change-45272 * Author: Myron Marston * Status: Closed * Priority: Normal * Assignee: Yui NARUSE * Category: core * Target version: current: 2.2.0 * ruby -v: ruby 2.1.0dev (2013-12-20 trunk 44301) [x86_64-darwin12.0] * Backport: 1.9.3: DONTNEED, 2.0.0: DONTNEED, 2.1: REQUIRED ---------------------------------------- Trying out ruby 2.1.0-rc1, I keep getting this warning. I understand why, and I've updated my ~/.zshrc to set RUBY_GC_HEAP_FREE_SLOTS for ruby 2.1, but I need to keep `RUBY_GC_HEAP_FREE_SLOTS` set for projects running on earlier versions. Ideally, this warning would only be emitted when RUBY_FREE_MIN is set and RUBY_GC_HEAP_FREE_SLOTS is not set. If RUBY_GC_HEAP_FREE_SLOTS is set, the programmer clearly knows that's the ENV var to use for 2.1, and likely needs to keep RUBY_FREE_MIN in place for running code against older rubies. After all, having RUBY_FREE_MIN set on 2.1 doesn't cause any problems, right? -- http://bugs.ruby-lang.org/