commit | 6952a8097885abac038a262aa42563b38b189415 | [log] [tgz] |
---|---|---|
author | Ömer Ağacan <omersa@google.com> | Fri Apr 11 04:14:04 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 11 04:14:04 2025 -0700 |
tree | 7ae11ebd87d58efe1b9d0852a2b6ff222c82469a | |
parent | 929657adc68bd2a9ddfc87e027433d4a06894ef8 [diff] |
[dart2wasm] JS interop: pass small ints as i31ref In V8, the only way to pass a Wasm integer or float to JS without allocation is by passing it as a 31-bit integer. This can be done by: 1. Passing as `i32`. If the integer fits into 31 bits it's passed without allocation. 2. Passing as externalized `i31ref`. (1) requires importing the JS function with different signatures: for each `int` argument we would need a signature with the `i32` as the Wasm argument type, and another with `externref` (or `f64` if we want to pass large integers as `f64`). This is not feasible as with a JS function with N `int` arguments we would need `2^N` imports. So we implement (2): we import each interop function with one signature, passing `externref` as the argument, as before. When the number fits into 31 bits we convert it to an `i31ref` and externalize it. Otherwise we convert the number to `externref` as before, by calling the JS function `(o) => o` imported with type `[f64] -> [externref]`. New benchmark checks `int` passing for small (31 bit) and large (larger than 31 bit) integers. Results before: WasmJSInterop.call.void.1ArgsSmi(RunTimeRaw): 0.020 ns. WasmJSInterop.call.void.1ArgsInt(RunTimeRaw): 0.018 ns. After: WasmJSInterop.call.void.1ArgsSmi(RunTimeRaw): 0.014 ns. WasmJSInterop.call.void.1ArgsInt(RunTimeRaw): 0.018 ns. Issue: https://github.com/dart-lang/sdk/issues/60357 Change-Id: I749001e0e7e9784114415439298c2f3e0fb974b3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/419880 Commit-Queue: Ömer Ağacan <omersa@google.com> Reviewed-by: 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.