From: k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at (Oberhumer Markus)
Message-Id: <199606301311.PAA09400@c210.edvz.uni-linz.ac.at>
Subject: Re: linking speedup ?
To: djgpp-workers AT delorie DOT com
Date: Sun, 30 Jun 1996 15:11:04 -0200 (MET DST)
Return-Read-To: markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at
Content-Type: text
Content-Length: 1042      

===============================================================================
Markus F.X.J. Oberhumer <markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at>

Subject: Re: linking speedup ?
To: djgpp-workers AT delorie DOT com
===============================================================================

***WARNING*** 

The patched stubify sometimes generates a damaged exetuable.
I haven't examined the problem, but maybe the next lines
should be changed:

!   if (drop_last_four_bytes && rbytes < 4096)
!     rbytes -= 4;

!   if (drop_last_four_bytes && rbytes < 4096)
!     rbytes = rbytes > 4 ? rbytes - 4 : 0;


Linking a large C++ program, I have observed the following 
speed improvements (very rough timings)

Original time: 40 secs

Enlarge transfer buffer of ld.exe to 64kB: ~ 10 secs faster
Use SmartDrv /N /F instead of /X switch:   ~ 10 secs faster
Use the patched stubify with 64kB buffer:  ~ 2 secs faster

So my linking time is now cut to half, nice !

I'd suggest setting ld.exe to 64kB by default or at least giving a
strong hint in the FAQ.