Date: Sun, 14 Sep 1997 22:40:56 -0400 (EDT)
Message-Id: <199709150240.WAA05042@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: billc AT blackmagic DOT tait DOT co DOT nz
CC: djgpp-workers AT delorie DOT com
In-reply-to: <199709150203.OAA17313@teleng1.tait.co.nz gatekeeper.tait.co.nz>
	(message from Bill Currie on Mon, 15 Sep 1997 13:58:35 +1100)
Subject: Re: Transfer buffer device driver
Precedence: bulk


> I suggested on Friday (nz) that maybe a device driver could be used 
> to provide a common transfer buffer for djgpp programs.
> 
> Well, as soon as I posted my message, I went off and implemented it 
> and the required changes to stub.asm.  The best (IMHO) feature of 

As much as this is an interesting idea to pursue, making the user
install (and run) yet another program is not a good idea.

If we change 2.02 crt[01] to locate a previous stub (even from 2.00 or
2.01 programs) and, if found, use it and resize its own stub to
minimum size, I think we'll have the best solution.  That lets us
expand one stub to 63.5K and leave the rest at 0.5k (or less?),
without any of them suffering from too-short-tb syndrome.

Not changing the stub means no problems with stubify, strip, or ld
changing the stub to an old version on us.