| commit | 643d1ba3d6a306f073ef62a248d29abe01f31fe6 | [log] [tgz] |
|---|---|---|
| author | Ömer Sinan Ağacan <omersa@google.com> | Tue Oct 22 14:47:08 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 22 14:47:08 2024 +0000 |
| tree | a1de84b1cf806c9f338ec775363f3191eeb168f6 | |
| parent | 2b899adb4c945e12941ed2e8959bfd9df7334f29 [diff] |
[dart2wasm] Check const-ness of instructions added to const exprs A constant expression in Wasm is an instruction sequence that consists of only the constant instructions. Currently if I generate a non-constant instruction in a constant expression I get an error during Wasm compilation. I then have to find where and how I generate the instruction, possibly by using `--watch <instruction offset>` passed to dart2wasm. With this change we check in an assertion that an instruction added to an instruction sequence for a constant expression can only be a constant expression. This helps with debugging as I notice the error earlier, and get a stack trace of the compiler function that generates the invalid instruction. Changes: - Add `bool get isConstant => false` member to `Instruction`. A method instead of field to avoid adding one more word to `Instruction` objects. - Override the member in constant instructions. - When creating an instructions builder, mark the builder as "constant", with an optional named constructor argument that defaults to `false`. - When adding an instruction to an instructions builder, check that if the instruction block is for a constant expression, the instruction is constant. Spec: https://webassembly.github.io/gc/core/valid/instructions.html#constant-expressions Change-Id: I59454f0634ab419a62f9455c84aa9ce631db8b63 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/391440 Commit-Queue: Ömer Ağacan <omersa@google.com> Reviewed-by: Slava Egorov <vegorov@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.