Rebuilding Optimizing Compiler for Dart
summary
History of the Dart compiler becomes concrete: a working AOT path is built from the JIT by using object-pool indirection and heap snapshots to serialize relocatable code, plus inline caching and field state tracking to move checks to definitions. Prototype AOT arrives in about 2–3 months, product-ready in a few more, enables Flutter on iOS, and cuts fallback code by sharing stubs so binaries shrink roughly 10–20%. Hot-site heuristics (≈1,000 hits) and regexp backend reuse are used to make it actually fast.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:14dynamic language
- 9:27type profiling
- 15:12non-classical
- 19:022014 tweaking things
- 25:07Object model mismatch
- 29:20JIT code is relocatable
- 32:00need replacement
- 35:41Dart Dev Compiler
- 36:43(2) every Dart tool has its own parser
- 37:182016 new type system & common front-end migration starts
related talks
31mBuilding optimising compiler for Dart
27mJavaScript as a compilation target - Making it fast
16mDart
47mWhy Google thinks you should drop everything you do and pick up their Dart.
24mKeynote: Dart in 2017 and beyond
04mWhy Dart?
36mOf JavaScript Ahead-Of-Time Compilation Performance
45mDart For the Language Enthusiast