🚀 go-pugleaf

In article <1992Oct15.003553.14620@news.Hawaii.Edu>, denault@galileo.ifa.hawaii.edu (Tony Denault) writes:
>The system stack register seem very limited due to its size restriction
>of 15 RAM locations. According to the manual it can handle up to 15
>long int, 7 DO loops or 15 JSR's or a combinations of these. This would
>make it seem rather easy to write a program with overflows the stack.
>I wrote a function which has 4 nested DO loop. I am very careful when to
>call it. It seem to me if I nest subroutine call and receive an interrupt,
>I could get in trouble very easily. 
>
>I don't use a C compiler. But I'm curious about how they handle subroutines
>calls. Do they use a separate stack for parameters and local storage? Is
>the Stack Register used for subroutine calls? Are nesting of subroutines
>calls and used of hardware DO loop used sparingly?

The following is valid for the Intermetrics 96002 C-compiler:

- The hardware stack is saved as part of the prologue in all C-functions that
  may call other functions.
- Parameters are passed on a software stack maintained by the code. An address
  register is reserved for use as software stack pointer (another address
  register is reserved for use as base pointer).
- This compiler *never* generates do-loops.
- There are no restrictions (other than RAM shortage) on the number of 
  function calls that can be executed.

-- 
** The above was the private opinions of Harald Ljo"en (harald.ljoeen@nta.no) **