From: vischne AT ibm DOT net
Subject: Time and motion studies of gcc and egcs and LCC
31 Jan 1998 21:53:09 -0800
Message-ID: <199802010537.FAA06136.cygnus.gnu-win32@out5.ibm.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
To: gnu-win32 AT cygnus DOT com

Somewhere in January's posts, there was a discussion of relative compiler
speeds under Windows 95/NT.  I replied that the same compilers on the
same machine running Linux are 2-3 times faster.  It occurred to me
afterwards that the probable reason for this is linking to a DLL library
or libraries for time-critical code.  If you get a profiler program that
lets you know where gcc spends its time, I think you'll find that gcc is
spending that extra time thunking back and forth between cygwin.dll.

If gcc were completely statically linked, or if you statically linked the
subset of cygwin.dll that is causing the slowdown, I'll bet you that, not
only gcc, but also time-critical programs like bash.exe would suddenly
show speed performances comparable to Unix.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".