Summary The V8 team is currently working on a new compiler pipeline that will help us bring future speedups to real-world JavaScript <https://v8project.blogspot.com/2016/12/how-v8-measures-real-world-performance.html>. In the next few weeks we will replace our current compiler architecture based on a non-optimizing (FullCodeGen) and optimizing compiler (Crankshaft) pair with the combination of an interpreter (Ignition) and a new optimizing compiler (TurboFan).
You can try the new pipeline by setting an about:flags entry <https://v8project.blogspot.de/2017/02/help-us-test-future-of-v8.html> or passing the flag "--future" to d8. Eng contact emails [email protected], [email protected] (TurboFan), [email protected] (Ignition) Design docs TurboFan: https://github.com/v8/v8/wiki/TurboFan Ignition: https://github.com/v8/v8/wiki/Interpreter Planned date for the switch March 2017. Affected platforms All How to try the new architecture This dedicated blog <https://v8project.blogspot.de/2017/02/help-us-test-future-of-v8.html> post describes how the new pipeline can be switched on. Debuggability DevTools support is the same as with the classic pipeline. Interoperability and Compatibility Risk There are no user-facing changes (e.g. no new APIs changed). The new pipeline will change V8's performance profile considerably. Real-world JavaScript performance <https://v8project.blogspot.de/2016/12/how-v8-measures-real-world-performance.html> should improve and V8 memory consumption should be reduced. We expect controlled regressions in some synthetic JavaScript benchmarks like Octane. We plan to purposefully address selected regressions in upcoming releases. We are already A/B testing the new pipeline to Canary and Dev channel in M58. Please note that individually, Ignition (on low memory devices and for certain JavaScript features on all platforms) and TurboFan (for certain JavaScript features) have been active for a long time (> half a year). Additionally we have set-up dedicated tests for security, correctness, performance and stability. How to report bugs As this is a major change in V8 we anticipate that unexpected, negative side-effects in performance, memory profile, security or correctness might occur. If you see anything, please feel encouraged to report a bug <https://bugs.chromium.org/p/v8/issues/entry?template=Bug%20report%20for%20the%20new%20pipeline> . If you have any concerns or remarks, please feel free to simply respond to this thread or send a mail directly to [email protected] Cheers, Michael -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
