| |||||||||||||
Tratt: Fast Enough VMs in Fast Enough TimeTratt: Fast Enough VMs in Fast Enough TimePosted Feb 11, 2012 3:53 UTC (Sat) by flewellyn (subscriber, #5047)In reply to: Tratt: Fast Enough VMs in Fast Enough Time by daglwn Parent article: Tratt: Fast Enough VMs in Fast Enough Time
Fascinating stuff. As far as the efficiency issues of tracing JIT go, I've been pondering the idea, and I wonder if it might be useful to have a combination of "method JIT" and tracing?
To wit, the system starts by creating compiled (but not necessarily highly optimized) versions of the functions, and then traces their execution and creates "trace-optimized" versions for common paths. This way, when the traced condition fails, you don't have to drop down to interpretation: you still have compiled code. It's just not as fast as the traced path.
I dunno, too much work? Difficult to automate?
(Log in to post comments)
Tratt: Fast Enough VMs in Fast Enough Time Posted Feb 11, 2012 16:50 UTC (Sat) by daglwn (subscriber, #65432) [Link]
This is essentially what HP's Dynamo project from the '90's did. The static compiler created PA RISC code (in this case it was optimized statically) and the Dynamo runtime took that code and translated it to PA RISC, optimizing it in the process given known runtime values. They saw good speedup.
|
|||||||||||||