[#23657] [Bug #1550] String#lstrip! raises RuntimeError on Frozen String Despite Making No Changes — Run Paint Run Run <redmine@...>

Bug #1550: String#lstrip! raises RuntimeError on Frozen String Despite Making No Changes

13 messages 2009/06/01

[#23729] [Bug #1583] Time + String no Longer Raises TypeError? — Run Paint Run Run <redmine@...>

Bug #1583: Time + String no Longer Raises TypeError?

14 messages 2009/06/05

[#23770] [Bug #1595] rake unusable on windows install — Robert Gonzalez <redmine@...>

Bug #1595: rake unusable on windows install

10 messages 2009/06/09

[#23869] [Bug #1640] [PATCH] Documentation for the Rational Class — Run Paint Run Run <redmine@...>

Bug #1640: [PATCH] Documentation for the Rational Class

12 messages 2009/06/16

[#23903] [Bug #1648] Rational#div Raises NoMethodError for Invalid Argument — Run Paint Run Run <redmine@...>

Bug #1648: Rational#div Raises NoMethodError for Invalid Argument

9 messages 2009/06/17

[#23977] [ANN] meeting log of RubyDeveloperKaigi20090622 — "Yugui (Yuki Sonoda)" <yugui@...>

Hi,

41 messages 2009/06/23
[#23979] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Run Paint Run Run <runrun@...> 2009/06/23

Thanks for the update. :-)

[#24173] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — "NARUSE, Yui" <naruse@...> 2009/07/07

Sorry for late response,

[#24174] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Luis Lavena <luislavena@...> 2009/07/07

On Tue, Jul 7, 2009 at 12:12 AM, NARUSE, Yui<naruse@airemix.jp> wrote:

[#24242] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Charles Oliver Nutter <headius@...> 2009/07/09

On Mon, Jul 6, 2009 at 10:18 PM, Luis Lavena<luislavena@gmail.com> wrote:

[#24010] [Bug #1685] Some windows unicode path issues remain — B Kelly <redmine@...>

Bug #1685: Some windows unicode path issues remain

26 messages 2009/06/24
[#29189] [Bug #1685] Some windows unicode path issues remain — Yuki Sonoda <redmine@...> 2010/04/01

Issue #1685 has been updated by Yuki Sonoda.

[#29200] Re: [Bug #1685] Some windows unicode path issues remain — Bill Kelly <billk@...> 2010/04/01

Yuki Sonoda wrote:

[#29892] Re: [Bug #1685] Some windows unicode path issues remain — Bill Kelly <billk@...> 2010/04/29

Hi,

[#24058] [Bug #1696] http downloads are unuseably slow — Steven Hartland <redmine@...>

Bug #1696: http downloads are unuseably slow

19 messages 2009/06/27

[#24063] [Feature #1697] Object#<=> — Marc-Andre Lafortune <redmine@...>

Feature #1697: Object#<=>

15 messages 2009/06/28

[ruby-core:23883] Merging recent Ruby threading improvements

From: Joe Damato <ice799@...>
Date: 2009-06-16 23:20:34 UTC
List: ruby-core #23883
Hi ruby-core and CC'ed friends -

As many of you know, Aman Gupta and I have been busy hacking on Ruby
1.8.{6,7} internals making some cool improvements with the threading
implementation.

We have some questions regarding next steps for some our work and what we
can do to help the Ruby community.

Currently, we have a threading implementation that moves the thread stacks
off of the process stack, reducing context switch cost significantly. More
technical information about this, as well as links to patches that apply
against Ruby 1.8.6 and 1.8.7 are available on my blog at:
http://timetobleed.com/fixing-threads-in-ruby-18-a-2-10x-performance-boost/

There are a few important things to note about the code provided there:

1.) The patches only build on the x86 and x86_64 platforms, other platforms
will likely fail to compile.
2.) The patches have only been tested on OSX and Linux on x86 and x86_64 -
other OSs will need to be tested.
3.) Currently, continuations are broken with our patches.

If Aman and I do the following items:

1.) Add #ifdefs to allow non x86 architectures to compile and use the old
thread code paths
2.) Test on a few more architectures (we would need help from the community
for this)
3.) Fix continuations

Will our code be considered for merging to future Ruby 1.8.{6,7} releases?

We ask this question because Aman and I hack on the Ruby interpreter for
*fun* - and completing the list of tasks above is not as fun as working on a
new GC implementation =]. We don't mind doing the work if we know before we
do it that we'll have the support of the community and that there is a
*reasonable* chance our code will get merged back in.

We look forward to working with the Ruby community moving forward -
Joe Damato and Aman Gupta

In This Thread

Prev Next