[dart2wasm] Add entry point annotations to fields of const classes
TFA works on kernel AST, when it encounters constants it asks the
`Target` for the implementation class of the constant and marks it
allocated. Though it doesn't automatically make fields of those classes
entry points.
That means if it sees a read of a field of such a class it may conclude
it's unreachable because it has never seen a write to it (the only
initialization may be the constant).
We could make TFA consider all fields of the const classes automatically
as entry points. Though Alex prefers to manually mark them.
In dart2wasm most const classes have their fields marked as
`@pragma('wasm:entry-point')` but the `_ConstSet` / `_ConstMap` were
missing.
In upcoming optimizations to TFA this will cause a problem, so we'll
mark them in this CL
Change-Id: I8249d4b36f0d6dde5ee398d5a617bc8e02a8ef8c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/519803
Reviewed-by: Slava Egorov <vegorov@google.com>
Commit-Queue: Martin Kustermann <kustermann@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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 in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.