[vm] Extend `analyze_snapshot` tool to emit more detailed information
In release builds most `Field` objects are tree shaken,
but if an instance field is e.g. a `late final` field then the `Field`
object is retained in the snapshot for the `LateInitializationError`
slow path. Though `Field` will not appear in `Class.fields()`, it
will only be referenced in the `ObjectPool`.
=> Instead of dumping `Class.fields()` we collect all `Field`s with
the same owner and dump those (a superset of `Class.fields()`)
We dump more information for a `Field`: Whether it's a reference field
or unboxed field (in which case we dump what unboxed type it is). We
also dump field flags (e.g. `late`, `final`, `static`).
We also dump now a `instance_slots` property on the class which
describes every slot in the instance. If a slot in an instance
* has a corresponding `Field` we emit `instance_field` type and
the id of the `Field` object.
* has no corresponding `Field` we emit a `unknown_slot` type
* we emit whether the slot is a reference field
This brings the information the `analyze_snapshot` tool dumps closer to
what Blutter uses, but some differences remain, e.g.:
* Blutter seems to scan constant instances of classes (if there's any)
and tries to determine based on those constants what unboxed slots
could mean.
It may look at 8 bytes and "guess" whether it's more likely to be an
integer or a double. (Side note: It doesn't consider
`Float32x4`/`Float64x2`)
=> The guess can be incorrect, so we do not do that.
* Blutter seems to scan constant instances of classes (if there's any)
and tries to guess the type of a reference field based on what that
constant's field points to.
=> The guess can be incorrect, so we do not do that.
go/dart-ama
TEST=vm/dart/analyze_snapshot_binary_test
Change-Id: I116560ba5e5f89d4349f2227362b8494e3af7a1c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/425261
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.