| commit | 08c802c7fc4e53363a6d9626349466a2285ef35f | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Fri Jan 31 00:58:00 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 31 00:58:00 2025 -0800 |
| tree | 974580c85927e013b112f3443b1f6b91ac33630f | |
| parent | a11aeeb5007bb118e49c60ff84c6edbfab4232a4 [diff] |
[CFE] Additions to benchmarker.dart et al ## Added --cache to benchmarker.dart This doubles the amount of runs by running an additional round of `perf stat` runs outputting low level cache information: L1-icache-load-misses (instruction load misses), LLC-loads (last level cache loads, i.e. probably how many loads goes to L3 cache) and LLC-load-misses (last level cache load misses, i.e. how many loads goes to ram). I don't know if these are generally available, only that they are available on my machine. ## Added --silent to benchmarker.dart Some benchmarks output information to stdout which is great when running it by hand, but when running it via the benchmarker script it just pollutes the output: The benchmarker script et al measures what is supposed to be measured. This CL adds the `--silent` option to the benchmarker script which then won't print the stdout output from the benchmarkee. ## Output filename in benchmarker.dart This CL adds the filenames of the benchmarked snapshots in an attempt to avoid confusion. Example output before: ``` Comparing snapshot #1 with snapshot #2 ``` ``` Example output now: Comparing snapshot #1 (optimization_attempt_41.aot) with snapshot #2 (optimization_attempt_42.aot) ``` ## Utility to summarize --verbose-gc output Takes input from --verbose-gc from stdin and summarizes the time taken on GC and reports it back. Example: ``` $ out/ReleaseX64/dart --verbose-gc hello.dart 2> /dev/stdout 1> /dev/null | out/ReleaseX64/dart pkg/front_end/tool/verbose_gc_helper.dart 6.1 ``` Change-Id: I206f21cd8b42f844e60358aed711e676e453c77c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/406845 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Jens Johansen <jensj@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.