Alexander Markov
e88728da87
Kernel file reader in Dart VM, when reading DirectPropertyGet referencing a method (not getter nor field), was ignoring receiver expression and was capturing 'this' to create tear-off. The implicit assumption receiver == 'this' for tear-offs in DirectPropertyGet is no longer true: devirtualization optimization can convert PropertyGet to DirectPropertyGet nodes for arbitrary receivers. This CL fixes handling of tear-off when reading DirectPropertyGet from kernel binary by checking receiver tag, and generating inline code for implicit closure allocation only when receiver is actually 'this'. Otheriwse, corresponding method extractor is obtained and called (directly). Issue: https://github.com/dart-lang/sdk/issues/30480 Change-Id: Ic8974e8cdcfb072ead8a27d6d5377dda4e4d0bd8 Reviewed-on: https://dart-review.googlesource.com/5560 Reviewed-by: Ryan Macnak <rmacnak@google.com> 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.