4be2981c2d
Right each `Pointer.fromFunction()` invocation will lead to creation of a new ffi trampoline function & it's following JITed code. In AOT we have exactly one ffi trampoline per target/native-signature/exceptional-return combination. => This CL ensures we have only one such function. Furthermore each `Pointer.fromFunction()` will currently perform 2 runtime calls in JIT: One to create a `Function` object, the other to JIT that function & register callback metadata. => This CL ensures we won't do a runtime call to get a function, instead do it at compile-time (as in AOT) Furthermore we eagerly assign a callback-id to the unique/deduped ffi trampoline callbacks. Only when the application requests a pointer, do we populate metadata on the `Thread` object. This CL doesn't (yet) change the fact that in JIT mode we have isolate-specific jit trampolines (that will call now shared ffi trampoline functions). We also avoid baking in C++ runtime function pointers in generated code. As a result we can now preserve ffi trampolines across AppJIT serialization. As a nice side-effect, we remove 100 lines of code. TEST=ffi{,_2}/ffi_callback_unique_test Issue https://github.com/dart-lang/sdk/issues/50611 Change-Id: I458831a47b041a088086f28f825de2a3849f6adc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/273420 Reviewed-by: Daco Harkes <dacoharkes@google.com> Commit-Queue: Martin Kustermann <kustermann@google.com> |
||
---|---|---|
.dart_tool | ||
.github | ||
benchmarks | ||
build | ||
docs | ||
pkg | ||
runtime | ||
samples | ||
sdk | ||
tests | ||
third_party | ||
tools | ||
utils | ||
.clang-format | ||
.gitattributes | ||
.gitconfig | ||
.gitignore | ||
.gn | ||
.mailmap | ||
.style.yapf | ||
.vpython | ||
AUTHORS | ||
BUILD.gn | ||
CHANGELOG.md | ||
codereview.settings | ||
CONTRIBUTING.md | ||
DEPS | ||
LICENSE | ||
OWNERS | ||
PATENT_GRANT | ||
PRESUBMIT.py | ||
README.dart-sdk | ||
README.md | ||
sdk_args.gni | ||
SECURITY.md | ||
WATCHLISTS |
Dart
A client-optimized language for fast apps on any platform
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).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
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).
Building Dart
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.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.