|author||Alexander Markov <email@example.com>||Thu Aug 18 20:46:34 2022 +0000|
|committer||Commit Bot <firstname.lastname@example.org>||Thu Aug 18 20:46:34 2022 +0000|
Revert "[vm/compiler] Initial implementation of IL binary serialization" This reverts commit 97004589756b0022bfdbb127c4ae0bc275f07b4b. Reason for revert: breaks Dart SDK build using gcc and dart-sdk-linux-main bot. Original change's description: > [vm/compiler] Initial implementation of IL binary serialization > > This change adds binary serialization/deserialization of flow graphs. > It supports all IL instructions and certain objects which can be > referenced from IL instructions. IL binary serialization is a useful > machanism which would allow us to split compilation into multiple parts > in order to parallelize AOT compilation. > > The program structure (libraries/classes/functions/fields) is not > serialized. It is assumed that reader and writer use the same > program structure. > > Caveats: > * FFI callbacks are not supported yet. > * Closure functions are not re-created when reading flow graph. > * Flow graph should be in SSA form (unoptimized flow graphs are not > supported). > * JIT mode is not supported (serializer currently assumes lazy > linking of native methods and empty ICData). > > In order to test IL serialization, --test_il_serialization VM option is > added to serialize and deserialize flow graph before generating code. > > TEST=vm/dart/splay_test now runs with --test_il_serialization. > > TEST=Manual run of vm-kernel-precomp-linux-debug-x64-try with > --test_il_serialization enabled (only ffi tests failed). > > Issue: https://github.com/dart-lang/sdk/issues/43299 > Change-Id: I7bbfd9e3a301e00c9cfbffa06b8f1f6c78a78470 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/254941 > Reviewed-by: Ryan Macnak <email@example.com> > Commit-Queue: Alexander Markov <firstname.lastname@example.org> > Reviewed-by: Slava Egorov <email@example.com> TBRfirstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com Change-Id: Iae4e4868f183815a8fc3cd79597141b3896e23d7 No-Presubmit: true No-Tree-Checks: true No-Try: true Issue: https://github.com/dart-lang/sdk/issues/43299 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/255780 Reviewed-by: Alexander Markov <firstname.lastname@example.org> Bot-Commit: Rubber Stamper <email@example.com> Commit-Queue: Alexander Markov <firstname.lastname@example.org>
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.
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.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
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.