Re: SPARC code generation for compiler course

I wrote:
> One important point is not to use the program stack for temporaries.
> The SPARC expects the stack structure to be consistent at all times so
> it can save overflow register windows properly.


Many readers have misinterpreted this statement. What I was actually
warning against was using the top of the stack for expression evaluation,
like in a real stack machine. Some of my students were doing this and
always getting their stack values clobbered by register saves. The top of
the stack must be kept ready to to hold saved registers. You can still,
of course, use the stack for holding local variables, as long as they are
only semi-dynamic.
--
Daniel J. Salomon -- salomon@cs.UManitoba.CA
              Dept. of Computer Science / University of Manitoba
              Winnipeg, Manitoba, Canada R3T 2N2 / (204) 474-8687
--

Return to the comp.compilers page.
Search the comp.compilers archives again.