d42de4ed06
This CL adds code to detect situations when we hit null error through GDT call with non-null receiver. We achieve this by making receiver's cid part of the GDT calling convention and checking this cid in runtime entry responsible for throwing the null error. This CL is an attempt to narrow down b/179632636 and collapse various impossible crash reports into a single native crash cluster by crashing VM instead of throwing a null error. TEST=tested manually Cq-Include-Trybots: luci.dart.try:vm-kernel-precomp-linux-release-x64-try,vm-kernel-precomp-linux-release-simarm-try,vm-kernel-precomp-linux-release-simarm64-try Change-Id: If2ed4646c4c0f403016266e4e83e296a7b234cb5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/191141 Auto-Submit: Vyacheslav Egorov <vegorov@google.com> Commit-Queue: Vyacheslav Egorov <vegorov@google.com> Reviewed-by: Martin Kustermann <kustermann@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.