| commit | af82cadcec3d2b5a487b6b09244c6afe481f8519 | [log] [tgz] |
|---|---|---|
| author | Vyacheslav Egorov <vegorov@google.com> | Mon Sep 09 15:03:09 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 09 15:03:09 2024 +0000 |
| tree | c9962da28aa09bc1fdc11df1ceebf50b1e904641 | |
| parent | 42a6ac431536e9801201728f5429aee5a0ad1432 [diff] |
[vm] Force inlining of various Struct helpers Specifically apply prefer-inline to: * All generated accessors. In general we almost always seem to select them for inlining through small-accessor heuristic, but sometimes it does not hit. Marking with pragma ensures that we are not dependent on specific heuristics to produce good code. * Various helpers involved in creating struct instances from typed data. These we *not* hit by normal heuristics and consequently not inlined prior to this change. Inlining them opens possibilities to fully eliminate allocations associated with `Struct.create(...)` if Struct does not escape. * Array creation helpers and accessors. They were also not inlined which meant we were producing unnecessary temporary objects when reading from inline arrays. TEST=/vm/dart/ffi_structs_optimizations_il_test CoreLibraryReviewExempt: no API or behavioral changes Cq-Include-Trybots: luci.dart.try:vm-aot-linux-product-x64-try,vm-aot-linux-release-x64-try Change-Id: I1650023200446bd5289118777365627ca19d3e5b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/384261 Commit-Queue: Slava Egorov <vegorov@google.com> Reviewed-by: Daco Harkes <dacoharkes@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.