From: Christoph <chr_news@...>
Date: 2002-08-16T15:52:41+09:00
Subject: Mswin32 build flags

Hi,

the current mswin32 build unfortunately (globally;-)
turns off the global optimization flag /Og, a real pit,
since using global optimization seems to result in ruby
binaries that (in some benchmarks) runs almost (together
with the "PURE_TEST != RTEST = inline method" compile
trick possibly) twice as fast as their ``stock compiled''
counter parts. (They are also faster than cygwin builds
btw.)

Unfortunately these builds also miserably fail the basic 
``nmake test'', however by only turning off the /Og 
flag turning the compilation of the file ``sprint.c'' 
one seems to get an executable which seem to enjoy
the speed gain of a full /Og optimization which 
passes the basic  "nmake test" (true at least for 
VC 7) - so I am wondering if there are known issues
against such a compilation strategy?
 

/Christoph