commit | 8df763f266c0bf7a2f4ca74926f513b7979c2398 | [log] [tgz] |
---|---|---|
author | Aske Simon Christensen <askesc@google.com> | Tue Feb 01 21:08:46 2022 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Feb 01 21:08:46 2022 +0000 |
tree | 3c4a9f7ebbe9318e950761e718b97031e0e1595c | |
parent | 534608fc66c086a93a11e51d4132a7fb13d0f06c [diff] |
Prepare for sharing TFA and patch files between the VM and dart2wasm. The VM patch files contain many annotations that guide the TFA and the VM compilation pipeline. Most of these are not relevant to dart2wasm, and having the TFA look at these when running inside dart2wasm leads to sub-optimal, and sometimes even unsound, results. In order to enable sharing of patch files between the VM and dart2wasm, the annotation parser is given a target flag to control which annotations it should recognize and how to parse them. The annotation parser thus becomes an abstraction layer between the concrete annotations in the patch files and the parsed annotations that the TFA sees. Additionally, external members used by dart2wasm don't always have external names. To support this, the signature shaker must skip all external members, not just the ones with an external name. This makes no difference for the VM, since all of its external members either have an external name or are implemented in a patch file, making them no longer external. TEST=ci + upcoming dart2wasm CL Change-Id: Id425dd1ccc5560721034ae83c8cdc1593801a4e5 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/231102 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Aske Simon Christensen <askesc@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.