Register-based VMs have a higher performance than stack-based VMs

Re:Register-based VMs have a higher performance than stack-b... by int_19h on Monday December 12, 2016 @05:49PM (#13162782)

An even shorter way to say this is that stack-based VMs are more high-level. With a register-based VM, you shift some important questions (like register allocation, and handling temporaries) to the compilers. With a stack-based VM, the compiler can be simpler, but the JIT will need to be correspondingly more complicated.

Which one to choose depends on how it is all used. For .NET, multi-language targeting was seen as an important design goal, and so making the bytecode easier to target was prioritized, with all the complexity relegated to JIT.

Long-term, I think it was a right solution in general, because most platforms seem to be moving from JIT to AOT; and with AOT, having the complexity in the bytecode-to-native compiler still has the upside of DRY, and slower compile times stop being a downside.

[ Parent | on HN ]

Re:Register-based VMs have a higher performance than stack-b... by AntonErtl on Tuesday December 13, 2016 @12:23PM (#13168539)

However, if you leave register allocation to the source->VM compiler and don't do it in the VM->machine compiler (JIT), you cannot perform machine-specific register allocation (8 registers on IA-32, 16 on AMD64 and ARM, 32 on Aarch64). So register-based VMs typically work with large register sets, and JITs allocate them to the smaller register sets of real machines.

I have not read the present paper yet, but earlier papers I have read were about reducing interpretation overhead by performing fewer VM instructions (if VM instruction dispatch is expensive; dynamic superinstructions make it cheap, but not everyone implements them).

[ Parent | on HN ]

Re:Register-based VMs have a higher performance than stack-b... by frjalex on Tuesday December 13, 2016 @10:51PM (#13173672)

Note that the JIT mechanism mentioned in the paper meant basically JIT from a program code to the bytecode executed in the VM, and directly executing it (very much like PHP), not necessarily directly to machine assembly.

[ Parent | on HN ]

Re:Register-based VMs have a higher performance than stack-b... by frjalex on Tuesday December 13, 2016 @10:41PM (#13173618)

Interesting.... the paper referenced you if you're the correct Anton Ertl :)

[ Parent | on HN ]