Alexander Markov
1f4707ae0c
Static (direct) calls in the optimized JIT are performed through Code objects without passing Function objects. This is not compatible with bytecode interpreter calling conventions, so optimized JIT should avoid static calls to bytecode functions. This change disables devirtualized and guarded static calls to functions declared in bytecode. TEST=ci Closes https://github.com/dart-lang/sdk/issues/60716 Change-Id: I95e4fa0706f376355f4fa7aea7fddf44f303e0a0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/428340 Reviewed-by: Slava Egorov <vegorov@google.com> Commit-Queue: 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.