from Hacker News

V8 Maglev: compiler design doc

by obl on 6/4/23, 10:14 AM with 17 comments

• by mkoubaa on 6/4/23, 12:59 PM

  Boy am I glad that huge internet companies are willing to fund these sorts of large engineering projects in the open

• by fulafel on 6/4/23, 11:42 AM

  Here's a recent post about shipping and results: https://blog.chromium.org/2023/06/how-chrome-achieved-high-s...

  Would be interesting to hear where they ended up with the parallelism that was mentioned in passing.

• by tambourine_man on 6/4/23, 11:57 AM

  This seems similar to Safari’s JSCore 4 tiers architecture.

  Imagine keeping execution smooth while switching between all those tiers. Modern JS engines are fascinating beasts.

• by taosx on 6/4/23, 11:01 AM

  Thank you to everyone involved in this. I'm wondering, is Node.js fiddling with v8 in order to focus more on the resulting code performance than the initial startup.

  Planning to learn C/C++ in order to investigate that and if there any gains there.

• by xt00 on 6/5/23, 1:13 AM

  Yay a new part of chromium with a new name made by different people (probably) than the original v8 people. Seems like Google has an affliction of “not invented by me”.

  Just read the first sentence if you are thinking I’m being a bit harsh:

  “We’ve previously made a case why four tiers in V8(Google internal) make sense to explain why Sparkplug made sense in addition to Ignition, TurboProp and TurboFan. TurboProp was a midtier compiler proposal based on TurboFan to significantly improve compilation speed while compromising on the performance of the resulting code. With Sparkplug in place, however, the design tradeoffs TurboProp made by being built on top of TurboFan didn’t end up panning out. ”

• by simonebrunozzi on 6/4/23, 2:29 PM

  Why pick a name - maglev - that will confuse everyone, forever?