| commit | 1a218c01036c738acb47cca637cf0cdb2b509a59 | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Thu Sep 11 05:33:04 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 11 05:33:04 2025 -0700 |
| tree | a51c3cbfc2e319a1d70b6041be02c7217f4544e8 | |
| parent | 48cc23ed130ce0b553394d26a6dccf9bacc3fc06 [diff] |
[kernel/CFE] Dill extractor tool; CFE compile dir tool; fixes for stats This CL adds two tools * A dill extractor tool which extracts the source files inside the dill to a new directory, trying to recrease the package config too so the sources can be compiled again. Thought as being useful for doing benchmarks between the CFE and the analyzer to make sure they look at the exact same source files. No more. No less. * A CFE compile entry point that compiles all files in a directory. Again thought as being useful to compare the CFE with the Analyzer. Additionally it introduces "--gcs=<int>" to `benchmarker.dart` so it can do multiple runs and do statistics on combined gc times. Usage example: ``` $ out/ReleaseX64/dart pkg/front_end/tool/compile.dart pkg/front_end/tool/compile.dart $ out/ReleaseX64/dart-sdk/bin/dart pkg/kernel/bin/dill_extractor.dart pkg/front_end/tool/compile.dart.dill /tmp/extracted_compile_dart_compile Done. Wrote 687 source files. $ out/ReleaseX64/dart-sdk/bin/dart compile aot-snapshot pkg/front_end/tool/compile_files_in_folders.dart Generated: [...]/pkg/front_end/tool/compile_files_in_folders.aot $ out/ReleaseX64/dart-sdk/bin/dart compile aot-snapshot pkg/analyzer_cli/bin/analyzer.dart Generated: [...]/pkg/analyzer_cli/bin/analyzer.aot $ time out/ReleaseX64/dart-sdk/bin/dartaotruntime pkg/front_end/tool/compile_files_in_folders.aot /tmp/extracted_compile_dart_compile/ Got 626 libraries. Finished in 0:00:03.496817 real 0m3.530s user 0m4.985s sys 0m0.257s $ time out/ReleaseX64/dart-sdk/bin/dartaotruntime pkg/analyzer_cli/bin/analyzer.aot /tmp/extracted_compile_dart_compile/ Analyzing /tmp/extracted_compile_dart_compile... warning • Target of URI doesn't exist: 'package:compiler/src/io/source_file.dart'. • package:_fe_analyzer_shared/src/scanner/utf8_bytes_scanner.dart:5:16 • uri_does_not_exist_in_doc_import 1 warning found. real 0m8.479s user 0m9.997s sys 0m1.048s $ out/ReleaseX64/dart pkg/front_end/tool/benchmarker.dart --silent --iterations=10 --gcs=5 --snapshot=pkg/front_end/tool/compile_files_in_folders.aot --snapshot=pkg/analyzer_cli/bin/analyzer.aot --arguments="/tmp/extracted_compile_dart_compile/" Will now run 10 iterations with 2 snapshots. .............................. Comparing snapshot #1 (compile_files_in_folders.aot) with snapshot #2 (analyzer.aot) msec task-clock:u: 141.1012% +/- 1.5550% (6281.55 +/- 69.22) (4451.81 -> 10733.36) page-faults:u: 47.5414% +/- 0.7786% (45602.90 +/- 746.84) (95922.50 -> 141525.40) cycles:u: 119.3182% +/- 1.5751% (22131655652.90 +/- 292155654.08) (18548436164.50 -> 40680091817.40) instructions:u: 140.2463% +/- 0.0340% (30410953910.60 +/- 7375789.67) (21683959961.20 -> 52094913871.80) branch-misses:u: 97.9816% +/- 7.3049% (73071988.00 +/- 5447773.30) (74577266.40 -> 147649254.40) seconds time elapsed: 141.0789% +/- 1.5479% (6.28 +/- 0.07) (4.45 -> 10.74) seconds user: 124.4165% +/- 1.8322% (5.31 +/- 0.08) (4.26 -> 9.57) seconds sys: 521.0422% +/- 17.4291% (0.98 +/- 0.03) (0.19 -> 1.16) Comparing GC: Combined GC time: 63.8901% +/- 1.2946% (1008.76 +/- 20.44) (1578.90 -> 2587.66) ``` (note that benchmarker passes `--deterministic` and limits the run to one cpu, both of which (potentially) makes it slower --- which is why the stats say 4.45 s instead of ~3.53 s and 10.74 s instead of ~8.48 s) Change-Id: I785620ce40af11ca1f7b6c88a0ac863b2200f7d3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/449180 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.