Samir Jindel
dea7de23bd
Test Plan: Behavioral correctness should be ensured by existing tests. Tests in vm/dart/entrypoints ensure that the unchecked entrypoint is used in cases where the optimization should trigger. Bug: https://github.com/dart-lang/sdk/issues/31798 Change-Id: I5b880b2dfa6343b4bb0a96ad23562facff73e41f Cq-Include-Trybots: luci.dart.try:vm-kernel-win-release-x64-try,vm-kernel-optcounter-threshold-linux-release-x64-try,vm-kernel-precomp-linux-debug-x64-try,vm-kernel-precomp-linux-release-simarm-try,vm-kernel-precomp-linux-release-simarm64-try,vm-kernel-precomp-linux-release-x64-try,vm-kernel-precomp-win-release-x64-try Reviewed-on: https://dart-review.googlesource.com/69741 Commit-Queue: Samir Jindel <sjindel@google.com> Reviewed-by: Vyacheslav Egorov <vegorov@google.com>
1006 B
VM-Specific Pragma Annotations
Pragmas for general use
These pragmas are part of the VM's API and are safe for use in external code.
-
vm:entry-point
[Defining entry-points into Dart code for an embedder or native methods] (file://../vm/compiler/aot/entry_points_pragma.md)
Pragmas for internal testing
These pragmas are used for inspecting or modifying internal VM state and should be used exclusively by SDK tests. They must be enabled with the --enable-testing-pragmas flag. The names of these pragmas are prefixed with "testing". Additionally, they are categorized into "safe" and "unsafe" forms: "safe" pragmas should not affect the behavior of the program and can be safely added anywhere. "unsafe" pragmas may change the code's behavior or may cause the VM to crash if used improperly.
-
vm:testing.unsafe.trace-entrypoints-fn
[Observing which flow-graph-level entry-point was used when a function was called] (file://../vm/compiler/frontend/entrypoints_pragma.md)