commit | b9b341f4a71b3ac8c9810eb24e318287798457ae | [log] [tgz] |
---|---|---|
author | Alexander Markov <alexmarkov@google.com> | Mon Mar 11 15:56:33 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 11 15:56:33 2024 +0000 |
tree | c706658604ad28944a0e7a2485d4b22eb079677d | |
parent | 8682ca72ce8aa9561f15fa859912acf95f7b0e32 [diff] |
[vm] Simplify and optimize method extractors Previously, method extractors (getter functions which return tear-offs) where implemented in the following way: Method extractor body is an asm intrinsic which loads a few registers and jumps to BuildMethodExtractor stubs. BuildMethodExtractor stub loads more registers, calls AllocateClosure stub and initializes a few fields of a closure (this stub also used to call AllocateContext but it is no longer needed for tear-offs). AllocateClosure allocates a closure object and initializes closure fields. Instead of doing 2 hops to the object allocation, method extractor body now calls AllocateClosure stubs directly which initializes all closure fields. This saves a jump and a handful of instructions to load certain things on registers and set closure fields. Assembler intrinsic for method extractor body and architecture-specific BuildMethodExtractor stubs are now removed. Also, as method extractors are really tiny, they are now always inlined. TEST=ci Change-Id: Icfeed18414659a76c7d24d3f6f53a76c91e5bbd3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/356302 Reviewed-by: Martin Kustermann <kustermann@google.com> Commit-Queue: Alexander Markov <alexmarkov@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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.