The IntelTM DX Math CoProcessor (MCP) is an extension of the IntelTM code compatible from the and math coprocessors Object code for . I recall my parents old computer having an empty socket for an Intel Math Coprocessor. I knew what it was for, but I always wondered if it. Coprocessor Basics. The 80×87 is able to multiply, divide, add, subtract, find the sqrt and calculate transcendental functions and logarithms. Data types include.

Author: Kajimi Goltisar
Country: Montserrat
Language: English (Spanish)
Genre: Environment
Published (Last): 24 December 2005
Pages: 166
PDF File Size: 10.63 Mb
ePub File Size: 1.42 Mb
ISBN: 743-9-43832-605-8
Downloads: 34810
Price: Free* [*Free Regsitration Required]
Uploader: Arakree

Flying Foxmorphine. About us Privacy policy Mailing list Mobile. Board index Hardware Processors. I knew what it was for, but I always wondered if it would have made games run faster. Would installing a math coprocessor made any difference in games, or does a piece of software have to be programmed to take advantage of it? The way they did this was clever, and took advantage of the fact that code memory was not write-protected coprcessor MS-DOS or early versions of Windows.

The generated code contained calls to runtime library routines which would emulate the x87 instructions in software. If the runtime library detected that an x87 was installed, it would go back and patch the code in memory to replace the library call with the corresponding x87 instruction. So the overhead of calling the emulator library was only incurred the first time a given piece of code was run after being loaded from 803887 after that, it ran at native x87 speed.

The encoding of an x87 instruction is shorter than a subroutine call, so the extra couple of bytes of code memory had to be backfilled with NOPs when the runtime library did the patching. But NOPs execute very fast, so it was close to native. You could optionally tell the compiler to assume that an x87 would always be coprocesdor, in which case it would just generate the x87 instructions from the get-go; in that case the runtime emulator and on-the-fly patching was not needed, and the code would shrink slightly but would crash if run on a system without an x Nostalgia isn’t what it used to be.

I successfully compiled a Linux Kernel by pure luck, kind of ocprocessor making the perfect chicken on a charcoal grill. So if a game were compiled by the MSDOS C compiler, would it have automatically detected the coprocessor and taken advantage of it? Or does support have to be enabled by the game programmer or be specifically programmed to be able to use it?


x87 – Wikipedia

I don’t know much about programming. I guess now it’s just doing the homework to find out which compiler game companies used on specific games, coproceseor out of curiosity. I’d like to know how much of my childhood was spent playing games where a math coprocessor wouldn’t have been sitting idle if the computer had one.

The biggies back then were Microsoft, Watcom, and Borland I’m just most familiar with the Microsoft one, since that’s the one I mostly used.

The Egg Minister of Gerbil Affairs. Now that I think about it, AMD might have actually made them up to 40mhz, coprocsssor still I’ve always had coproceszor affinity for the era of PCs, and specifically thought it would be cool to have a DX with a co-processor and maxed out RAM. Skill 2x16GB M. Though I don’t know how tangible the difference would have been. Might have thrown it out last year though The feeling that you’ve heard this bull before.

If I recall, the DX models had x87 built-in. The DX had the x87 coprocessor built in. Almost certain the DX did not. The i math coprocessor was not ready in time for the introduction of theand so many of the early motherboards instead 8387 a socket and hardware logic to make use of an The original Compaq Deskpro is an example of such design.

Intel 80387SX

However, this was coproceszor annoyance to those who depended on floating point performance, as the performance advantages of the over the were significant.

Pancake Gerbil First Class. By default the Microsoft C compiler for MS-DOS and early Windows versions generated code which could be patched on the fly to take advantage of an x87 coprocessor if it was present. I have 3 CPUs that I can run in it: I’m currently using the AMD chip because I 08387 been able to get the Cyrix to upgrade chip to 83087 reliably yet.

It has a few pins that relate to cache control it has 1KB of on-chip cache! I did see an increase in speed in synthetic x87 FPU benchmarks though. Some things that I learned while researching this: The Cyrix CPU, however can conditionally still execute instructions if they are in the cache, while the FPU does its thing, since it does not need to access the external data bus in this case!


Also, to clarify, the only difference between a SX and DX is a bit vs. I’m about to try a few things with the cache control registers on the Cyrix chip right now to see if I can get it working, and I might also run a few benchmarks with and without the FPU enabled while I’m at it. I’ll post the results here. Cyrix at a later time did make another upgrade chip called the CxDrx2, which was clock-doubled and also had supporting circuitry on-package to fix the cache coherency issues that the earlier chips like mine suffered from.

Once dad realized he could use 10 times more points on screen with little loss in processing power his drawings got a lot more complex. About a year later we moved to a dx-2 Core I7 K 4.

It was in the DOS time so I have tested them alland You could run Turbo Pascal without any coprocessor but it was really slow. These coprocessors were not great if you compare here: I started with a math coprocessor with Turbo Pascal and Mandelbrot fractals.

I had one, and it wasn’t fast. There is a fixed amount of intelligence on the planet, and the population keeps growing: Aye, foprocessor SX was bit internally, bit externally. Real people used config. Humans sleep soundly in their beds because rough cats stand ready in the night to visit violence on those who would do us harm.

One of the best tech companies to appear and disappear – extended memory management when Intel processors only allowed K to be addressed; windowed multi-tasking when even Microsoft Windows could not do that – a real pioneer! I recall my parents old computer having an empty socket for an Intel Math Copfocessor. Who is online Users browsing this forum: No registered users and 0 guests.