Re: Optimizing stack access for a stack based VM

Alex McDonald wrote:


>>There are separate address space for (1) code, (2) data, (3) stack.
>
> The separation between code and data isn't required in Forth (although
> there may be advantages in certain architectures that treat each space
> differently, or don't like mixing of code and data).


IMO Forth is not a direct solution for the OP, since...


> "Variables" in Forth are words that push their addresses on the stack,
> as in the @ and ! example given above. Forth also has a value, or a
> self fetching variable.


Forth has no local variables (for recursive calls), the implementation
of e.g. loop counters requires two separate stacks, for data and
return addresses. Calling subroutines (Forth: compiled words) for the
retrieval of references to variables IMO also is overkill, in a VM
other than the Forth machine itself.


Nonetheless Forth is a source of inspiration, for everybody who wants
to learn more about really uncommon virtual machines :-)


DoDi

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