Path: utzoo!attcan!uunet!zephyr.ens.tek.com!tekchips!sail!toma
From: toma@sail.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Where is "gcc" for the MSDOS?
Message-ID: <8842@sail.LABS.TEK.COM>
Date: 25 Jan 91 00:32:38 GMT
References: <2612@trlluna.trl.oz> <2946@sixhub.UUCP> <326@stiatl.UUCP>
Reply-To: toma@sail.LABS.TEK.COM (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 34

In article <326@stiatl.UUCP> tok@stiatl.UUCP (Terry Kane) writes:
>davidsen@sixhub.UUCP (Wm E. Davidsen Jr) writes:
>
>>In article <2612@trlluna.trl.oz> hui@shiva.trl.oz (Alvaro Hui) writes:
>>|    Did anyone know where is "gcc" for the MSDOS is??
>>|    I prefer it to be ftpable.
>>  I just got a new version today, look for it in the near future if it's
>>any good. This is g++, so it's C and C++.
>Has gcc(++) been ported to DOS, really?  And if so, will it be acceptable
>in performance - both runtime and results?

I've got a copy here. I compiled XLISP with it. Both it and the generated
binaries run under 386 protected mode using a supplied "dos extender".
Compared to Metaware High-C and PharLap Dos Extender:

1. About 1% slower.
2. Fewer DOS functions ported. In particular you can't write interupt
   routines or spawn DOS processes. I had to manually add some missing
   functions (stty and get/set break).
3. The Library is pretty barren.
4. No control over FP traps.
5. VM doesn't seem to work.
6. If you want to distribute commercially, the extender is $5/copy, if
   you use FSF it is free. The compiler is free. The Metaware/PharLap
   combo is $3000 w.o VM.

It's fairly easy to live with the problems!



-- 
Tom Almy
toma@sail.labs.tek.com <<< Note new address
Standard Disclaimers Apply