Vyacheslav Egorov
2c97d724df
CloneContext is implemented as a runtime call so it is considerably slower than AllocateContext which leads to performance issues in loops that capture iteration variables in for loops. Lowering CloneContext into AllocateUninitializedContext and a sequence of explicit load&store instructions both improves the performance by avoiding the runtime call and also makes CloneContext semantics exposed to store-load forwarding and allocation sinking. PutIfAbsent benchmark from issue #31113 is improved by 5x, while ForInGeneratedLoop benchmark is improved by 8x. Bug: https://github.com/dart-lang/sdk/issues/31113 Change-Id: I03fdede75f1a85fda92487aa8f9307ce06f23903 Reviewed-on: https://dart-review.googlesource.com/16280 Commit-Queue: Vyacheslav Egorov <vegorov@google.com> Reviewed-by: Alexander Markov <alexmarkov@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.