Related articles |
---|
Activation Records on Stack Based Machines io@spunge.org (2004-01-22) |
Re: Activation Records on Stack Based Machines torbenm@diku.dk (2004-01-31) |
Re: Activation Records on Stack Based Machines anton@mips.complang.tuwien.ac.at (2004-01-31) |
Re: Activation Records on Stack Based Machines basile-news@starynkevitch.net (Basile Starynkevitch \[news\]) (2004-01-31) |
Re: Activation Records on Stack Based Machines joachim.durchholz@web.de (Joachim Durchholz) (2004-02-01) |
Re: Activation Records on Stack Based Machines ftu@fi.uu.nl (2004-02-01) |
Re: Activation Records on Stack Based Machines rbates@southwind.net (Rodney M. Bates) (2004-02-04) |
From: | io@spunge.org (leibniz) |
Newsgroups: | comp.compilers |
Date: | 22 Jan 2004 23:11:52 -0500 |
Organization: | http://groups.google.com |
Keywords: | architecture, question |
Posted-Date: | 22 Jan 2004 23:11:52 EST |
Hello,
I'm actually new to code generation techniques dealing with
function invocation/declaration. I am working on a small imperative
language that uses a stack based virtual machine. I've searched/read
about activation records, but all I found was register-based machines
way of pushing activation records on the stack. Where do I place the
return value of a function, save program counter, allocate space for
local variables...etc. Can someone give me pointers on how that can be
done on stack-based machines? Or even documents that explain how
Python, Java, or any other language that uses a stack-based VM
implements activation records?
regards,
Return to the
comp.compilers page.
Search the
comp.compilers archives again.