[#41916] Proposal: Bitmap Marking GC — Narihiro Nakamura <authornari@...>

Hi.

18 messages 2012/01/05

[#41941] [ruby-trunk - Bug #5851][Open] make check fails when compiling with GCC 4.7 - *** longjmp causes uninitialized stack frame *** — Vit Ondruch <v.ondruch@...>

12 messages 2012/01/06

[#41979] [ruby-trunk - Bug #5865][Open] Exception#== should return false if the classes differ — Hiro Asari <asari.ruby@...>

10 messages 2012/01/08

[#42003] [ruby-trunk - Bug #5871][Open] regexp \W matches some word characters when inside a case-insensitive character class — Gareth Adams <gareth@...>

14 messages 2012/01/09

[#42016] [ruby-trunk - Feature #5873][Open] Adopt FFI over DL — Heesob Park <phasis@...>

15 messages 2012/01/10

[#42149] [ruby-trunk - Feature #5899][Open] chaining comparsions. — Ondrej Bilka <neleai@...>

12 messages 2012/01/16

[#42164] [ruby-trunk - Feature #5903][Open] Optimize st_table (take 2) — Yura Sokolov <funny.falcon@...>

18 messages 2012/01/17

[ruby-core:41927] Re: Proposal: Bitmap Marking GC

From: KOSAKI Motohiro <kosaki.motohiro@...>
Date: 2012-01-05 20:12:17 UTC
List: ruby-core #41927
>> And, GC is a little bit slower. But, I think it's in acceptable range.
>
> Maybe you could/should make GC collector type user specifiable, to
> avoid the slowdown [this is what REE does I think].
> For instance on windows you don't need it.

I disagree. all of 'selectability' is just work around. Almost people don't
know GC internal so much. thus, they can't choose right gc so easily.
The right way is, many developers run his new gc and join his optimization
work. We definitely need only one fastest gc.

In This Thread