![]() The [Environment] represents 2 different things: * before (env, deopt-id): The state of unoptimized frame right before the IL instruction is executed * after (env, deopt-id): The state of unoptimized frame right after the call machine instruction instruction (i.e. which may not be after the IL instruction - as it may still have to drop arguments) The environment's prune-count specifies the number of entries from the [Environment] to be removed to get from before-env to after-env. This prune-count includes generally most of `<IR>::InputCount()` - as most IR instructions consume their inputs (which location summary may e.g. require in registers) before doing any call. Though it doesn't include arguments as we currently have a stack-based calling convention and both optimized and unoptimized code will explicitly drop them after the machine call instruction. Our optimizing compiler may emit speculative instructions. Those will receive an environment that makes before (env, deopt-id) and after (env, deopt-id) the same - as both eager and lazy deopt will target a before (env, deopt-id). => We should ensure that the prune-count is set to 0, ensuring we won't prune anything in case an IL instruction was marked with `MarkAsLazyDeoptToBeforeDeoptId`. => This is a preparation for inlining force-optimized functions: If we inline them and some callee IL instruction performs lazy deopt it should re-try the call without any pruned inputs. TEST=ci Change-Id: I091c9fa962b376200dc5cfb6ea8c9a47ef43810f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/319440 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Slava Egorov <vegorov@google.com> |
||
---|---|---|
.dart_tool | ||
.github | ||
benchmarks | ||
build | ||
docs | ||
pkg | ||
runtime | ||
samples | ||
sdk | ||
tests | ||
third_party | ||
tools | ||
utils | ||
.clang-format | ||
.gitattributes | ||
.gitconfig | ||
.gitignore | ||
.gn | ||
.mailmap | ||
.style.yapf | ||
.vpython | ||
AUTHORS | ||
BUILD.gn | ||
CHANGELOG.md | ||
codereview.settings | ||
CONTRIBUTING.md | ||
DEPS | ||
LICENSE | ||
OWNERS | ||
PATENT_GRANT | ||
PRESUBMIT.py | ||
README.dart-sdk | ||
README.md | ||
sdk.code-workspace | ||
sdk_args.gni | ||
SECURITY.md | ||
WATCHLISTS |
Dart
A client-optimized language for fast apps on any platform
Dart is:
-
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
-
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
-
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
-
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
-
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
Building Dart
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.