Alexander Markov
14f6276945
Devirtualization optimization now adds metadata to kernel AST instead of transforming nodes to Direct* ones. The direct call metadata provides information about checking receiver for null, while Direct* kernel nodes do not support null checking. VM's kernel binary loader is extended to extract arbitrary metadata from kernel binaries and keep it for flow graph builder. Kernel flow graph builder is extended to take direct call metadata into account and generate CheckNull/StaticCall instructions for devirtualized PropertyGet, PropertySet and MethodInvocation nodes. Issue: https://github.com/dart-lang/sdk/issues/30480 Change-Id: I57f56fbf4a8981d33b1571c0d93105cf8ca71d76 Reviewed-on: https://dart-review.googlesource.com/12260 Reviewed-by: Vyacheslav Egorov <vegorov@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.