Free Software Foundation * 675 Mass. Ave. * Cambridge, MA 02139 * USA * Tel: (617) 876-3296 * Email: fsf@prep.ai.mit.edu
Commercial support (and enhancements) available from:
Cygnus Support * 814 University Avenue * Palo Alto, CA 94301 * Tel: +1 415 322 3811 * Fax: +1 415 322 3270 * email: info@cygnus.com
Single unit $1500 for 1 year technical support. Educational and volume discounts available. Cygnus Support is the official maintainer of GNU C++ for the Free Software Foundation.
host: grape.ecs.clarkson.edu * login: ftp * password: send your e-mail address * directory: ftp/pub/msdos/djgpp
As a convenience to non-FTP users, djgpp is also stored on Clarkson's archive server, sun.soe.clarkson.edu. To access the archive server, do this:
mail archive-server@sun.soe.clarkson.edu * Subject: <none> * help * index msdos/djgpp * ^D
For other copyright ( or copyleft ) instructions please see the previous subsection.
Supported Wares:
Re: The DOS port of GCC (called djgcc).
Basically its great. It is the only (free or reasonably
priced) C/C++ compiler that allows you to access upto 128meg
easily. The optimization and code generated is much better
than Borland and the 386 code runs upto 30% faster for simple
math.
- There is a group on usenet for problems, announcements
(name = ???)
- I believe that the graphics is done with late linking
(I have not gotten it to work yet) which is a bit of a
pain for the S/W I have been writing (it trys to detect
what the video HW is from a variety of 16 mfg's).
- It does not have an extensive debugger/profiler like Borland
but I am sure that it may already be done or on its way.
- Being able to access that much memory (and it will swap to
disk so you don't have to worry about that either) and all
of the proven GCC optimizing etc make it very useful for
anyone who need access to > 640k (like when I was doing a
lot of matrix work a while ago).
I hope this helps.
- Eric
From: Kai Henningsen(Kai_Henningsen@ms.maus.de)
Re: Why some PC C compilers ar.....
kr> Von : kjb@cgl.rmit.oz.au (Fr, 15.05.92 03:30)
kr> Name: Kendall Bennett
kr> Box : RMIT Computer Centre, Melbourne Australia.
kr> MId : <kjb.705897037@godzilla.cgl.citri.edu.au>
kr> RId : <92-05-062@gnusenet.comp.compilers>
kr> thing I did when I first installed DJGPP for my
kr> PC (running under DOS naturally) was to run tests
kr> on this program. It took about twice as long or more
kr> to compile under DJGPP, and the resulting program ran
kr> horrendously slow. I set up file approx. 1Mb in size,
kr> to be translated, and the times were...
kr> BC++: 9.2 seconds
kr> DJGPP: > 40 seconds
I'm not astonished. Did you look at how DJGPP does I/O? No?
Don't look there, you might get nightmares! :-)
What it does is, first, everything goes through the DJ/GNU/
BSD-Libraries; then, when it arrives at the actual read()/
write(), it calls an interrupt which is intercepted by the
driver. The driver, in turn, calls Borland's read()/write()
routines, which may even do a (very slow) cr/lf<->lf translation.
No wonder it's slow.
By the way, last I checked, the same handling is what broke
timezone handling for DJGPP: because it's broken in Borland's
Turbo C.
In both cases, double libs make the problem much worse.
MfG Kai