News for hackers. Stuff that matters.

A comment on Ignition: V8 Interpreter. Parent comment

Re:Ignition: V8 Interpreter by mike_hearn on Monday August 10, 2015 @04:04PM (#10036936)
Not that unusual. In fact the planned architecture sounds exactly like HotSpot: a fast assembly based interpreter that profiles the code, with tiered fast/slow compilers producing machine code for hot spots, with deoptimization support to allow more speculative optimisations.

It actually seems a bit of a shame that V8 and Nashorn are competing despite heading towards very similar architectures.

[ Parent | on HN ]
Re:Ignition: V8 Interpreter by vitalyd on Monday August 10, 2015 @09:49PM (#10038664)
I got the same impression from a cursory read. Profiling in the interpreter has its downsides, chief among them is lack of inlining causing profiles sometimes to be less useful. Tiered compilation can help here, but requires more careful code cache management.
[ Parent | on HN ]
Re:Ignition: V8 Interpreter by gsg on Tuesday August 11, 2015 @01:45AM (#10039296)
Having TurboFan compile the interpreter from machine-independent templates is what struck me as unusual.

The rest is familiar enough, true.

[ Parent | on HN ]
Re:Ignition: V8 Interpreter by mike_hearn on Wednesday August 12, 2015 @08:45AM (#10047381)
The HotSpot interpreter is done the same way, I believe. It's also a template based interpreter.
[ Parent | on HN ]