Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!labrea!decwrl!decvax!ucbvax!cbosgd!mandrill!abvax!harmon
From: harmon@abvax.icd.ab.com (Larry Harmon)
Newsgroups: comp.sys.m6809
Subject: Re: os9 C compiler and Disk cache request
Message-ID: <51@abvax.icd.ab.com>
Date: Thu, 3-Sep-87 08:11:29 EDT
Article-I.D.: abvax.51
Posted: Thu Sep  3 08:11:29 1987
Date-Received: Sat, 5-Sep-87 17:02:04 EDT
References: <596@potpourri.UUCP>
Distribution: na
Organization: Allen-Bradley Company, Inc; Industrial Computer Division, Highland Heights, OH
Lines: 17
Keywords: C  cache
Summary: can't pipe asm or link passes

In article <596@potpourri.UUCP>, csantiag@potpourri.UUCP (Carlos Santiago) writes:
> 
>  Can someone please explain pipe the different parts of the C compiler
> together? I am running Level II on a CoCo 3 with 512k and 2 40 track double
> sided drives. I tried to pipe the files together, but the c.asm module had
> problems finding the assembly source.
> 
	Well I'm afraid you just can't pipe the assemble or link steps of the
C compiler.  My approach has been to pipe the preprocessor, pass1, and pass2
steps leaving the output in a temporary file with the same name cc1 would have
given it, then finish the compile (asm and link) exactly the same way cc1 would.
	It would be great to be able to pipe the whole process but, even piping
the first half at least doubles the speed of the process.  If the C passes are
all resident in memory and pipes are used a three to four times speed increase
is achieved.  I would be interested to know how using a ram disk such as the
external DISTRO would affect the speed.  Anyone doing this?
							Larry Harmon