The only actual change required to the profiler service is appropriately retrieving the source position for interpreted frames during processing. Otherwise, most of the tests just need small changes to account for the slightly different stack trace generated by interpreted code when walking the stack as code instead of functions: * Interpreted code calls the runtime entry DRT_AllocateObject directly for slow-path allocation instead of via the AllocateObjectSlow stub. * The current name for bytecode frames when walked as code starts with "[Bytecode]" instead of "[Unoptimized]". The test vm/cc/Profiler_GetSourceReport is skipped since: * It tests compiled code-specific features like classifying source positions. * Inserting fake samples for interpreted functions is messier since many PC offsets may map to the same source position. The other skipped tests are specific to inlining and/or optimized compiled code, so there's no point in running them on interpreted code. TEST=vm/cc/Profiler Cq-Include-Trybots: luci.dart.try:vm-dyn-linux-debug-x64-try Change-Id: I3e73f42b2562eb6e3e73fe8d5c3f14389039ee04 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/507082 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Tess Strickland <sstrickl@google.com>
Dart
An approachable, portable, and productive language for high-quality apps on any platform
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).
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 in our repo at docs.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Roadmap
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.