From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: Where does gcc -o foo make foo.exe
Date: Fri, 19 Jan 2001 18:44:45 +0100
Message-ID: <NEBBIOJNGMKPNOBKHCGHIEMLCAAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3A672C29.25210.292C34@localhost>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id MAA28007
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> I also notice the field used by bfd/coff-stgo32.c (bfd->usrdata) to hold the 
> stub is for use by applications, not for backends like DJGPP COFF. I also 
> notice ld makes use of this field. Yet another reason to overhaul stubbed 
> COFF support.
And we could make use of the opportunity to try and get the stub-handling code
to support variable-sized stubs, so PMODE/UPX/custom stubs can be used. This
seems to be non-trivial though; I couldn't find anything in bfd (at first
glance) that suggested it could handle objects with headers of variable size.