delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:6052 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: 387 emulation slowed down *a lot* |
Date: | Tue, 16 Jul 1996 08:36:19 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 11 |
Message-ID: | <31eb9ad3.sandmann@clio.rice.edu> |
References: | <4sdt9p$djj AT news2 DOT delphi DOT com> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> Has there been a major change in the way floating point instructions > are intercepted in this version? Anything I can do? Essentially a complete re-write. FPU emulation didn't work with V1.x under DPMI. When I did FPU emulation in V2, my goal was to make it work with a minimum of code and effort. So I used the signal library, which took about 3 lines of code. This isn't the fastest way, which would require some assembly glue to hook in, etc. Since FPUs are essentially free now, I couldn't justify spending an extra 10 minutes on it. If you want to hack on NPXSETUP, you can probably make it faster. But it's probably easier to find a 387 or 486DX ...
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |