06183779d7
We already make the callsites use dyn:* selectors for normal method calls as well as setters, this is doing the same thing for getters. Once callsites use dyn:get:* various pieces in runtime need to be adjusted to accomodate for that (e.g. NSM handling, etc). A follow-up CL will then start actually generating dyn:* getters in certain situations. Issue https://github.com/dart-lang/sdk/issues/40876 Change-Id: If219603bc0b8eb119edd08b211a8897d21ec0fb6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/154320 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Tess Strickland <sstrickl@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.