From: Paul Brannan <pbrannan@...>
Date: 2003-04-03T23:29:49+09:00
Subject: Re: SIGSEGV and crash in $std***.print

On Thu, Apr 03, 2003 at 02:05:25PM +0900, nobu.nokada@softhome.net wrote:
> I meant the former, but yes, gcc-3's optimization seems wicked
> for current ruby GC implementation as you mentioned.

In what way is gcc-3's optimization wicked?  What workarounds are there
for extension writers?

Because Ruby searches the stack in its mark phase, I've considered that
perhaps ruby.h should change:

typedef unsigned long VALUE;

to:

typedef volatile unsigned long VALUE;

This should keep the compiler from optimizing away any references on the
stack.

Paul