[vm,dyn_modules] Add native entry fallbacks for FFI callback creation.
In compiled code, static calls to FFI callback creation functions are
replaced with different IL, so those functions should never be called
from compiled code and so the code assigned to them always errors.
For the creation of callbacks in interpreted JIT code, this CL replaces
the always-erroring definitions with native entries that check that the
caller is interpreted and running in JIT mode and, if so, creates an FFI
callback and returns it. In AOT mode and for other callers, the native
entry returns an error as before.
This CL also weakens the return check for native entries when dynamic
modules are enabled to allow for returning Function objects as well as
Instances. These FFI callback creation functions are only called from
transformed code, and so the returned Function object is consumed in
the transformed code and never returned to user code.
There are still some issues remaining with isolate group bound
callbacks and async callbacks that are exposed by removing the
"This function should be handled at the callsite." error. Those
will be addressed in followups.
TEST=RTE->Pass:
ffi/function_callbacks
ffi/isolate_local_function_callbacks
ffi/vmspecific_function_callbacks
ffi/native_callables
(and many more)
RTE->Crash:
ffi/async_void_function_callbacks
ffi/isolate_group_bound_callback
ffi/vmspecific_handle_test
ffi/regress_jump_to_frame
ffi/threading_reentrant_test
RTE->Timeout:
ffi/threading_test
Cq-Include-Trybots: luci.dart.try:vm-dyn-linux-debug-x64-try,vm-dyn-mac-debug-arm64-try
Change-Id: I4e5c9d76c2720db8543b835c81d5f317b1811cb9
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/525281
Commit-Queue: Tess Strickland <sstrickl@google.com>
Reviewed-by: 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 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.