commit | f53af0d445c8f73562274bcea9e0bec394a1f6a0 | [log] [tgz] |
---|---|---|
author | Daco Harkes <dacoharkes@google.com> | Thu May 06 13:22:22 2021 +0000 |
committer | commit-bot@chromium.org <commit-bot@chromium.org> | Thu May 06 13:22:22 2021 +0000 |
tree | b27c69dcd24a47dbf7cd22888dc4de9ca166d569 | |
parent | c6f69d8829e0f6ccc7f952a5844ac5a11dbafdbb [diff] |
[cfe/ffi] FFI transformation support incremental compilation The compounds transformation converting fields into getters and setters now retains the annotations on the getters so that they can be read during recompilation. This splits up `_replaceFields` into `_findFields` and `_replaceFields`. `_findFields` works for both transformed and non-transformed compounds. This splits up `_compoundClassDependencies` out from `_checkFieldAnnotations`. The former is run on all compounds transitively reached from the compounds being compiled, the latter only on the compounds being (re)compiled. `manualVisitInTopologicalOrder` now visits compounds from all libraries, not just the ones in the libraries being (re)compiled. It is responsible for filling the `compoundCache` in topological order. And, this CL introduces the `InvalidNativeTypeCfe` to support processing compounds with invalid fields, which might be nested later in other compounds. Bug: https://github.com/dart-lang/sdk/issues/45899 TEST=pkg/front_end/testcases/incremental/crash_05.yaml TEST=tests/ffi(_2)/* Change-Id: I07a2214fd460f4d5e6a84df81e8b140dd80401dc Cq-Include-Trybots: luci.dart.try:vm-precomp-ffi-qemu-linux-release-arm-try,vm-ffi-android-debug-arm64-try,vm-kernel-precomp-linux-debug-x64-try,vm-kernel-precomp-linux-debug-x64c-try,vm-kernel-reload-linux-debug-x64-try,vm-kernel-reload-rollback-linux-debug-x64-try Fixed: 45899 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/198281 Commit-Queue: Daco Harkes <dacoharkes@google.com> Reviewed-by: Jens Johansen <jensj@google.com>
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).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
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).
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.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.