V8’s Turbofan Compiler Completes Migration from Sea of Nodes to Turboshaft
After more than a decade, V8’s flagship optimizing compiler, Turbofan, has abandoned the Sea of Nodes (SoN) intermediate representation. The team behind Google’s JavaScript engine announced that the entire JavaScript backend now uses Turboshaft, a control-flow graph (CFG) based IR. The move addresses long-standing performance cliffs, architectual debt, and limitations in Crankshaft, Turbofan’s predecessor.
Background
Sea of Nodes was introduced in 2013 with Turbofan to replace the Crankshaft compiler. At the time, it enabled speculative optimizations and handling of asm.js code. However, over the years, SoN proved difficult to maintain and extend. “We hit a wall where adding new features required patches in four separate assembly backends,” said a V8 engineer familiar with the transition. “Turboshaft lets us express optimizations more naturally, without those hard-coded paths.”
The shift began three years ago. Since then, the team has systematically replaced SoN-based components. Now, Turboshaft powers the entire JavaScript backend and the full WebAssembly pipeline. Only two legacy parts remain on SoN: the builtin pipeline, being gradually reworked, and the JavaScript frontend, which is being replaced by Maglev – another CFG IR.
What This Means
For JavaScript developers, the change promises more consistent performance. Crankshaft suffered from dozens of bailout scenarios that could tank speed by a factor of 100. Turboshaft eliminates many of those pitfalls. “We expect real-world apps to see fewer janky slowdowns, especially when using modern ES features,” the engineer noted.
WebAssembly, already fully on Turboshaft, will benefit from the same reliability. The unified CFG representation also simplifies future work: new optimizations like instruction combining or loop unrolling can be added once and apply across both JS and Wasm pipelines.
Key Improvements Over Sea of Nodes
- No more hand-written assembly for every architecture. Turboshaft uses a shared lowering layer, reducing the need for per-ISA code.
- Support for new control flow during lowering. High-level operations can now be expanded into conditional branches, enabling better specialization (e.g., adding strings vs. numbers).
- Elimination of deoptimization loops. Turboshaft tracks assumptions more accurately, preventing repeated re-optimization cycles.
- Full try-catch support. A feature that had stumped Crankshaft engineers for months is now naturally handled.
“We’re still in the process of retiring the last SoN components,” said the V8 team in a statement. “But the transition is on track, and we’re already seeing cleaner code and faster iteration times.”
Developers can expect the final switch to complete by the end of the year, with Maglev taking over the JavaScript frontend. The move cements V8’s commitment to a simpler, more maintainable compiler infrastructure.
For more details, see the original blog post: Land Ahoy: Leaving the Sea of Nodes.