🚀 go-pugleaf

In article <8512061148.AA25696@ucbvax.berkeley.edu> terrell@OHIO-STATE.CSNET (Eric Terrell) writes:
>Does anyone know what to do about the "out of registers" error message
>in the HIPPO-C compiler?
>
Yes.  It will occur whenever a subroutine call requires too many
registers to hold all the intermediate results before putting them
on the stack.  Someone's register reclemation algorithm could
use a little fine tuning.  In particular, constructs like

	a = foo(bar[i].left, bar[i].right, ... );

will get the error.  However, it can be recoded as

	t1 = bar[i].left;
	t2 = bar[i].right;
	...
	a = foo(t1, t2, ... );

What a hack eh?
>Also, is it possible to start up with the original disk and then change
>to a copy of the disk?  With my single-drive system I am currently
>unable to use the compiler unless I use the original disk (yuk!)
Oh yes.. There is documentation on how to do this supplied with the
compiler, but..

	(a) initialize a new disk
	(b) copy everything but hos.tos to this new disk. DO NOT
	    USE A SECTOR COPY.
	(c) To run, boot on HOS.TOS on the supplied disk, eject it
	    and insert your copy.  You should do a 'ls' to get the
	    new disk directory information set up properly.

NOTE: If you have a one drive system, go an borrow a 2 drive one for
step (b).  There are 40 or so files that have to be copied, 3 disk
swaps per file = 120 disk swaps.

They suggest that you do not use a sector copy.  I would assume that
their protection mechanism either (i) will cause the sector copy to
abort, or (ii) foul up the protection on their disk.
-- 
--
Michael Jenkin					University of Toronto
USENET:	{decvax,ihnp4,allegra}!utcsri!utai!jenkin
CSNET:	jenkin@Toronto 
BELL: 	416-978-7321