Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 exptools; site ihwpt.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!ihwpt!knudsen
From: knudsen@ihwpt.UUCP (mike knudsen)
Newsgroups: net.micro.6809
Subject: Re: C compiler strange errors
Message-ID: <776@ihwpt.UUCP>
Date: Fri, 21-Mar-86 12:34:21 EST
Article-I.D.: ihwpt.776
Posted: Fri Mar 21 12:34:21 1986
Date-Received: Sat, 22-Mar-86 21:58:28 EST
Distribution: net
Organization: AT&T Bell Laboratories
Lines: 23

Thanks to those who have responded to my question
about mysterious C.link errors.  Some say it is due
to Pass2 running out of disk space, others to Pass1 running
out of RAM.  Both may be correct; on my flakey Coco,
I can sometimes get a bogus "out of storage" error from
Pass1.  I say bogus because it happens on a file that
never had the problem before.  However, it beats the more common
spontaneous re-boots as noted in another posting.
Sooner or later I get lucky and get a REAL compile.

As for disk space, sometimes disk writes abort early
and leave a truncated version of the file, which would
certainly look to the Assembler like Pass2 ran out of
disk space.

BTW, your RAM space during Pass1 gets eaten up by any
global or static variables in your file (unless extern).
So big arrays or structures should not be put with large
source files.  Really big arrays would have to be faked
with alloc() and malloc(), I guess.  Anybody out there
ever try those and live?

mike k