Jens Johansen
3932452322
Follow-up to https://dart-review.googlesource.com/c/sdk/+/384540 allowing the removal of bounds checks for `String.codeUnitAt` if the method it is called from is annotated with `@pragma('vm:unsafe:no-bounds-checks')`. Done by the inliner providing the calling function to the flow graph builder and GenericCheckBound instruction utilizing this information. TEST=Existing tests; added runtime/tests/vm/dart/no_bound_check_il_test.dart Change-Id: Ic6144b0b8400ec6532fb58cd5fd9b3dcdb9a2ff9 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/385201 Reviewed-by: Slava Egorov <vegorov@google.com> Commit-Queue: Jens Johansen <jensj@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.