🚀 go-pugleaf

My guess as to Scott's puzzle:

	When the array is small enough to fit into the stack everything is
fine.  When the array is large enough to almost fill the stack the local
variables used by the "printf" function cause the stack to overwrite the
Transputer reserved memory locations at the bottom of the address space.  When
the array is larger than the stack the local variables used by "printf"
clobber somewhere else (most Transputer hardware vendors leave high order unused
address lines uncommitted, this causes the physical address space to be
mirrored through out the logical address space...)  The solution: make the
stack allocation large enough for the program being run!  Also remember that
many library routines will require stack space also.  Allowing 1K bytes of
stack per LSC library function invocation is a safe assumption, although many
library routines use far less.  In general I suggest making the stack MUCH
larger than really needed during the program development phase and only
worrying about stack size and placement during final program optimization
(assuming that optimization is really justified by the application!)

	Cheers,
		Kirk Bailey
		Logical Systems