| commit | f2929bfd51f9b84cd9ac286ff4ce098a1b848cfe | [log] [tgz] |
|---|---|---|
| author | Martin Kustermann <kustermann@google.com> | Mon Jan 20 04:52:01 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 20 04:52:01 2025 -0800 |
| tree | a1fd13d1c929130f423714e708138496c56e4968 | |
| parent | a565406ecca2fb1be648e5532cd24dcf21d45012 [diff] |
[dartwasm] Do not preserve details for errors in --minify, move throwing code to (not inlined) slow path * We outline throwing code to never-inlined function * We inline index/range checking code using fast unsigned compares * We omit details in `--minify` mode The support for omitting details in `--minify` means that the signature shaking pass will remove all parameters of the slow paths in `--minify` mode, making them functions with no arguments that just throw a constant as an exception. Together these changes result in smaller code for common data structures that do index/range checks. Which can have positive effects downstream (e.g. less to inline for wasm runtimes). This leads to around this (in -O2) FluteComplex.Compile.Size.wasm.opt -0.514 % FluteComplex.Compile.Size.wasm.opt.gz -1.664 % Hello.Compile.Size.wasm -2.298 % Hello.Compile.Size.wasm.opt.gz -4.864 % It also leads to (in -O2) around 10% perf improvement on `TypedDataPoly.*` benchmarks. Issue https://github.com/dart-lang/sdk/issues/54395 Change-Id: Icd1cdf28a061f7763bd4bac7cfd5eaeea150c469 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/404301 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Ömer Ağacan <omersa@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.