From: nobu.nokada@...
Date: 2002-03-21T18:10:45+09:00
Subject: Re: Some Windows (re | bench)marks (Re: building latest cvs ruby on win)

Hi,

At Thu, 21 Mar 2002 13:04:47 +0900,
Christoph wrote:
> Thank you very much for the quick fix ... however there an old build
> problem (under VS6 and VS7) still remains  The culprit is
> 
> mswin32-ruby17.def (generated by mkexport.rb).
> 
> The offending lines look like
> 
> ---
> ....
> SafeFree
> Win32System
> _real@0000000000000000
> _real@3eb0c6f7a0b5ed8d
> ....
> _real@bff0000000000000
> _real@c1d0000000000000
> chown
> closedir
> ....
> ----

Hmm, they should be rejected by /@.*@/.  Is it better to change
/@[0-9a-f]{16,}$/?

> Using a full /Ox optimization (this includes a frame-pointer optimization)
> removes all of the non-readable symbols from the export list and adds
> another  ~ 10 - 15 % speed improvement in my test script below.
> Unfortunately running ``nmake test'' (or installing) uncovers a problem with
> printf - for example

But it crashes with `nmake test'.  Obviously critical bugs are
still there.

> The biggest performance booster is a switch of compliers: Using the
> VS7-C++  compiler over a  VS6-C++ compiler results in a executable
> which is a whopping  ~75 % faster (in my test case that is).
> To put in  perspective:  A ``VS7-C++ & /Ox'' compiled cvs-Ruby  is
> 
> ~   10 % faster as an aggressively complied Cygwin cvs-Ruby.
> ~ 100 % faster as VS6-C++ compiled cvs-Ruby (with stock optimizations)
> ~ 150 % faster than the current Prag-Prog Ruby

Sounds great, but I don't have VS7 and am not the maintainer
for mswin32, talk with Usa about it.

-- 
Nobu Nakada