Sigmund Cherem
44f8e21c82
Introduce a helper library to trim components based on what we believe it is needed for modular bytecode compilation. The script is configured to accept a set of entry points, so unreachable libraries can be removed entirely. The contents of the retained libraries is trimmed to remove method bodies, constructor bodies, and initializers, except for where they may be needed. In the near future, this should be expanded to: * include proper unit testing in the CFE * review whether additional trimming operations can be made * consider an explicit representation of trimmed content, to help the CFE recover when assumptions are not met (e.g. sentinel markers to establish whether a value has been trimmed) * CFE produces trimmed data directly if needed, without having to first produce the full dill. Tests that specifically stress that we don't over-trim include: apply_mixin (requires preserving method bodies), const_body (requires preserving initializers). TEST=existing and new e2e dynamic module aot tests. b/394936876 Change-Id: I26db8385bdfe1664b2aea234ec8bb896c7c21230 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/418702 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Sigmund Cherem <sigmund@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com>
Tests for Dart dynamic modules
This folder contains tests for an experiment of implementing dynamic modules in Dart. All tests are written in the style of the language end-to-end tests.
Folder structure
Each folder consists of a single test scenario. You'll find 4 kinds of files:
-
main.dart: the host application that will later load dynamic modules. This will be the core driver of the test. -
shared/: folder containing multiple libraries with code that can be used by both the host application and dynamic modules. -
modules/: folder containing code private to dynamic modules. It includes libraries with common code as well as an entrypoint file per dynamic module. Entrypoint files are namedentryN.dartand must define an exported dynamic module entrypoint. Note: semantics limit that two dynamic modules can't share code unless they are compiled in a chained fashion, currently the test harness focuses on compiling modules in isolation and ensuring conflicts don't arise. -
dynamic_interface.yaml: a contract specifying what parts of the host application and libraries inshared/are visible to dynamic modules.
Execution
We've build a test framework that frontloads compilation, so that execution of the test can be streamlined. This means that:
-
The host app will be compiled first, using
dynamic_interface.yamlas a specification for AOT compilers. -
Each and every dynamic module entrypoint in
modules/will be compiled to create a dynamic module artifact. -
Finally an execution environment will be launched that will in turn load each dynamic module as prompted by the test logic.
Commands to drive the loading and execution of each dynamic module are
controlled by a helper library in ../common/testing.dart, which
uses the Dart SDK API and abstracts away differences between platforms.
Example
Refer to update_top_level. This is one of the simplest tests that illustrates
the utilities and concepts in this framework.