Modestas Valauskas
c5d547fdb8
When the unoptimized code of a function exceeds 1 MB, start its optimized compile with far_branch_level=1 instead of 0. Without this, the assembler fails on out-of-range conditional branches at level=0, longjmps out of the optimizing pipeline, and the whole pipeline reruns at level=1 from scratch. Measured on a naive 49 KLOC generated lexer with --huge_method_cutoff gates lifted: JIT compile drops from ~26.6s to ~13.2s (about 50%). Work towards https://github.com/dart-lang/sdk/issues/63230 TEST=ci Change-Id: I2608a23ef899603a46b401b71be7322b7a8dd44b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/506120 Auto-Submit: Modestas Valauskas <valauskasmodestas@gmail.com> Reviewed-by: Martin Kustermann <kustermann@google.com> Reviewed-by: Slava Egorov <vegorov@google.com> Commit-Queue: Slava 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.