| commit | 7a29aa5984cb7c46408a04c09b4eefb1d1bb9c48 | [log] [tgz] |
|---|---|---|
| author | Ömer Sinan Ağacan <omersa@google.com> | Thu Aug 17 11:18:39 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 17 11:18:39 2023 +0000 |
| tree | 9c11890508a0fc708821490b31e9c2dea3bb1f89 | |
| parent | 51ac43644d153a778097fe4f82b8e3a1902750f4 [diff] |
[dart2wasm] Simplify Error._throw
I can't find a public documentation of Binaryen's type merging pass, but
the code clearly states in [1] that merging isn't observable.
So we can remove the assumption in `Error._throw` that type merging can
merge unrelated struct types, and use a Wasm type test for checking if
the thrown object is an `Error`.
After this, Binaryen inlines all `Error._throw`s in some programs and
removes the definition.
Inlining `Error._throw` in turn removes some `unreachable`s. Example:
Before:
(func $IndexError.check ...
...
(if
...
(call $Error._throw
(local.get $3)
(call $StackTrace.current))
(unreachable)))
After:
(func $IndexError.check ...
...
(if
...
(local.set $4
(call $StackTrace.current))
(if
(ref.is_null
(struct.get $IndexError 2
(local.get $3)))
(struct.set $IndexError 2
(local.get $3)
(local.get $4)))
(throw $tag$0
(local.get $3)
(local.get $4))))
[1]: https://github.com/WebAssembly/binaryen/blob/0fc7b883d373924717ceccf71a6a759c97a8fb08/src/passes/TypeMerging.cpp#L18-L19
Change-Id: Ic635cf008435829043cd19306039659d894b0149
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/319401
Reviewed-by: Aske Simon Christensen <askesc@google.com>
Commit-Queue: Ömer Ağacan <omersa@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.