bmeurer
Re:V8 is going to switch to a new compiler architecture after 5.8 bran...
on Thursday February 23, 2017 @01:31PM (#13716369)
I'm not sure if you are referring to a particular optimization, but speaking of
https://twitter.com/bmeurer/status/834677090381348865
and
https://twitter.com/bmeurer/status/834668611180625921
the "Bazinga!" event in both cases refers to two very specific fixes that addressed deoptimization loops in TurboFan. The more interesting steady increase in performance is due to long-term real-world performance work, especially in the area of data-driven ICs (inline caches) and function context specialization.
We will follow up with more details about Ignition and TurboFan, and the whole new code generation architecture soon.
Re:V8 is going to switch to a new compiler architecture after 5.8 bran...
on Thursday February 23, 2017 @12:44PM (#13715885)
So far the feedback from Node.js users/developers indicates that the --future configuration is a net win. There are some cases where performance degrades, and we are actively working on those. Instructions how to test-drive --future with Node.js can be found here: https://medium.com/@bmeurer/help-us-test-the-future-of-node-...
Re:Bringing ChakraCore to Linux and OS X
on Thursday July 28, 2016 @04:57AM (#12179142)
TurboFan is shipping for functions with try/catch or try/finally.