Alexander Aprelev
0914835773
Builds on top of https://dart-review.googlesource.com/c/sdk/+/228660, introduces vm:vm:always-consider-inlining that tell inliner not to give up inlining of a function. HashMap constructor got prefer-inline pragma to accommodate shift in inlining away from where it used to be inlined due to large size of inlined HashMap, greater than FLAG_inline_getters_setters_smaller_than heuristic. Notable performance changes: JIT (x64) === ListCopy.List.of.fixed.100 27.37% ListCopy.List.of.fixed.2 16.31% AOT (x64) === Empty -9.978% InstantiateTypeArgs.Instantiate1 -8.262% ... ListCopy.List.of.fixed.2 13.73% ListCopy.spread.num.2 15.51% ListCopy.List.of.2 15.08% MapCopy.Map.String.of.Map.100 55.62% MapCopy.Map.Thing.of.Map.100 56.06% flutter release === flutter_gallery_apk_size (Pixel 2) -0.0074% (1.0 noise)41809568.00 41812676.00 Addresses https://github.com/dart-lang/sdk/issues/49408 TEST=Inliner_always_consider_inlining, Inliner_List_of_inlined Change-Id: I7f8fc7cb0ac4a69310c108cf519518c384dc0164 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/253740 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Alexander Aprelev <aam@google.com>
Dart VM Compilation Pipeline
This folder contains Dart VM compilation pipeline.
Compilation pipeline is mainly responsible for converting AST or Kernel AST into IL flow graphs and then generating native code from IL.
It has the following structure:
| Directory | What goes there |
|---|---|
assembler/ |
Assemblers and disassemblers |
backend/ |
IL based compilation backend: optimization passes and architecture specific code generation rules |
frontend/ |
Frontends responsible for converting AST into IL |
jit/ |
JIT specific passes and compilation pipeline entry points |
aot/ |
AOT specific passes and compilation pipeline entry points |
. |
Shared code or code without clear designation. |
Currently there are no layering restrictions and components from different subfolders can reference each other.