From: Bram Stolk <bram AT nuson DOT nl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: FYI: speed of Allegro/DJGPP
Date: Mon, 27 Oct 1997 13:01:25 +0100
Organization: Nuson Inspection Services b.v.
Message-ID: <34548295.731EF500@nuson.nl>
References: <62msre$rc0$c AT 195 DOT 26 DOT 68 DOT 19> <345066F3 DOT 7D1C AT vxl DOT imag DOT net> <34524B87 DOT 6FFD AT stud DOT warande DOT ruu DOT nl>
NNTP-Posting-Host: nuson.nl
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 27
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Hi,

Elliott Oti wrote:

> IMO an important bottleneck in the speed of gcc is the fact that the
> preprocessor, compiler, assembler and linker are all separate programs
> that communicate via temp. files, making disk IO speed the bottleneck.

This is definately NOT a gcc bottleneck.
It is a DJGPP bottleneck.

Gcc on a proper OS (read: UNIX) supports the -pipe flag.
Check out the gcc man pages.

With this option, a preprocessor, compiler, assembler, linkerloader are
all started simultaneously, and communicate with IPC (pipes).

This is especially a very cool option to use if you have a
multiprocessor
machine, and enough ram.

I used to compile my sources with DJGPP.
Now I crosscompile them from Linux, WITH the -pipe flag.
Together with the much better filesystem linux has, my
compilation times have almost vanished :-)

   Bram