1574e860c8
Could for instance be run like this: out/ReleaseX64/dart pkg/front_end/tool/flame/instrumenter.dart pkg/front_end/tool/_fasta/compile.dart out/ReleaseX64/dart pkg/front_end/tool/_fasta/compile.dart.dill.instrumented.dill --omit-platform pkg/front_end/tool/_fasta/compile.dart out/ReleaseX64/dart pkg/front_end/tool/flame/instrumenter.dart pkg/front_end/tool/_fasta/compile.dart --candidates=cfe_compile_trace_candidates.txt out/ReleaseX64/dart pkg/front_end/tool/_fasta/compile.dart.dill.instrumented.dill --omit-platform pkg/front_end/tool/_fasta/compile.dart out/ReleaseX64/dart pkg/front_end/tool/flame/instrumenter.dart pkg/front_end/tool/_fasta/compile.dart --candidates=cfe_compile_trace_candidates_subsequent.txt out/ReleaseX64/dart pkg/front_end/tool/_fasta/compile.dart.dill.instrumented.dill --omit-platform pkg/front_end/tool/_fasta/compile.dart * The first command compiles and instruments "compile.dart" to record all procedure calls. * The second command runs the instrumented compiler on "compile.dart" (but it could have compiled anything). Because every procedure is instrumented this will take a lot longer than a usual run. This produces a trace "cfe_compile_trace.txt" with every call taking at least 1000 microseconds. This can be displayed via Chromes about://tracing tool. It also produces a file "cfe_compile_trace_candidates.txt" with a map of the procedures that on average took at least 500 microseconds. * The third command compiles and instruments "compile.dart", this time only instrumenting the procedures mentioned in the map "cfe_compile_trace_candidates.txt". * The forth command runs the instrumented compiler on "compile.dart". This run shouldn't take significantly longer than a non-instrumented run. It produces a new "cfe_compile_trace.txt" which this time is not filtered. It also produces a file "cfe_compile_trace_candidates_subsequent.txt" of recorded procedures that on average took at least 50 microseconds. * The fifth and sixth commands repeats the third and forth but instrumenting only the procedures mention in "cfe_compile_trace_candidates_subsequent.txt". The third iteration might not be needed, but if the first run was on a smaller input (which it isn't in this example) there might be some calls that on average took long enough to be included in the candidate list because the first call was slow and there were only very few of them, making the second trace very big because there are now a lot of - as it turns out - very quick calls recorded. Adding the third iteration will filter (at least some of) those out. Change-Id: I702c5c9142e525502b02f37744fcdc9d2b0f9b20 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/296902 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@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.