From:	Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com>
Subject:	Re: GO32 leaving, here comes ???
To:	peb AT pine DOT dk (Per Baekgaard)
Date:	Thu, 8 Jun 1995 09:22:33 -0500 (CDT)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu (DJGPP Mailing List)

> > 4) Loads 387 emulator if needed
> > 
> > In V2, virtually all of the functions above are handled in 32 bit GCC
> > or GAS code intead of Go32 code built with TCC.
> 
> Does that include loading the emulator? Or is emulation done directly
> by -lm or something similar (like in MS-C)?

In V2, you can link in the emulator library with -lemu (before -lc) or by 
default allow emu387.dxe to be dynamically loaded at execution time if needed.
Linking with -lemu makes image distribution simpler, and adds about 20Kb
to the size of the image (but still is not used unless needed).  The emulator 
can be either DJ's or WM's (both have been ported and tested).  The "387"
environment variable is treated the same as in V1.x, which allows you to
test emulation on systems with coprocessors.

Currently you must have a coprocessor to use the debugger with floating
code, and it will probably stay that way until I get some time, unfortunately.

- Raw text -