4 ms·
This was the toolchain used to build and ship Quake. Prior to that id, like everyone used Watcom C/C++ with the DOS/4GW extender.
by epcoa 3y ago
This was the toolchain used to build and ship Quake. Prior to that id, like everyone used Watcom C/C++ with the DOS/4GW extender.
- mysterydip 3y agoWhat prompted the switch? Was performance improved?
- epcoa 3y agoPerformance was not improved directly, gcc was terrible. Gcc development had actually stagnated for basically all of the early 90s and there was considerable discontent leading to a long forgotten but high profile fork: egcs. This work eventually went back into gcc for the 3.0 major version and the development model evolved considerably but this was well after the development of Quake. Short story Watcom had superior codegen throughout this time and for years later. The performance critical parts of quake were written in Pentium micro optimized assembly. Using DJGPP gave other advantages, the id team developed on Unix/Next boxes. I think they also had some commercial Unix servers for running the expensive level (PVS) compilers. This gave them had a compiler that could target Unixen, DOS and windows. They could ship the compiler if they wanted (though ultimately mods were done through quake C). With source available they were able to and did in fact modify the compiler and DOS extender for their needs as well https://en.m.wikipedia.org/wiki/CWSDPMI https://en.m.wikipedia.org/wiki/CWSDPMI (See CWSDPR0)
- pjmlp 3y agoNeXTSTEP to be more precise.
- flopsamjetsam 3y ago> long forgotten but high profile fork: egcs Thanks for the reminder of the name. I was trying to think of this a couple of days ago.
- royjacobs 3y agoSee also: https://groups.google.com/g/comp.os.msdos.djgpp/c/VD-mIK56h74/m/P5zE_uabjnEJ https://groups.google.com/g/comp.os.msdos.djgpp/c/VD-mIK56h7...