commit | 302885c467144f064481df43bd9154477f100c5e | [log] [tgz] |
---|---|---|
author | Martin Kustermann <kustermann@google.com> | Thu Apr 10 06:01:48 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 10 06:01:48 2025 -0700 |
tree | aaec51495e14823be57ad1437f4463ca36cceda5 | |
parent | 727c0e5ee20246ab676d4722b79982c78de75ffa [diff] |
[dart2wasm] Smaller `as T` type checks due to less inlining Currently we are quite agressive when inlining `as T` type checks. This is due to a number of `@pragma('wasm:prefer-inline')` annotations combined with `@pragma('wasm:static-dispatch')` annotations causing us to generate polymorphic dispatcher functions for calls to `_Type._checkInstance`, combined with the polymorphic call target force inlining targets with <= 2 specializations. These combination of factors lead to a `x as T` to become something like <... code for checking x & T's nullability ...> classId = x.classId; if classId = ClassId.getClassId(_InterfaceClass) ... else ... This lead to binaryen sometimes infer the `x.classId` value to be a constant which prunes the branches which then calls the faster path for interface type checks. Though this is quite a lot of code size. So instead of inlining all these things, but still taking advantage of the binaryen global optimizations that may infer `x.classId` we load the class id (which binaryen may sometimes turn into a constant) and then pass it to the polymorphic dispatcher (which we no longer inline to safe code size). This way if the class id is a constant, either binaryen or V8 will see that it can inline the polymorphic dispatcher as most of its body disappears if the class id is known. Since we no longer inline the polyhmorphic dispatcher, we can now also mark other common types via `@pragma('wasm:static-dispatch')` - such as `_RecordType._checkInstance`. This in return will speed up any code that uses records in collections (e.g. in maps / sets / lists) as the covariance checks now involve loading class id and branching on it to a devirtualized `_RecordType._checkInstance` instead of an indirect call that also involves a function type check). We also remove the `@pragma('wasm:prefer-inline')` on the `_checkSubclassRelationshipViaTable` function: The idea was that if binaryen infers the load of class id most of the code that follows can be optimized away at compile time. Unfortunately the tables can get large, which made us not use `ImmutableWasmArray` but instead normal `WasmArray`. That in return makes binaryen unable to optimize loads from it (at constant index) away, as the contents of the array may change (they never do, but binaryen doesn't know that). So there's little benefit in inlining it. Change-Id: I416fbdd35c6425a626378f2e9ea2009e50bf600b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/420320 Reviewed-by: Ömer Ağacan <omersa@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.