| commit | 5ad31d95bb673b4e8b8104b5dbed28683570f30d | [log] [tgz] |
|---|---|---|
| author | Jens Johansen <jensj@google.com> | Fri Jun 21 10:06:08 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 21 10:06:08 2024 +0000 |
| tree | 3674b83756d8c25f43298f87672c64a50d0d9420 | |
| parent | 2c11a8b2cc0cd978a683ac84cea337e32b7b134a [diff] |
[CFE] Fix outline_suite time-regression on using generateKernelInternal in expectation tests
After 9a9b33eb0b950dec7524274e1eb06beb2e7ff020 running the outline suite
got noticeably slower.
For whatever reason it wasn't noticed until now though.
```
$ out/ReleaseX64/dart pkg/front_end/test/fasta/outline_suite.dart --traceStepTiming
[...]
[ 05:02 | 100.0% | + 2914 | - 0 ]: outline/wildcard_variables/unnamed_optional_parameter_no_default
check errors: 0:00:00.301055 ms
ErrorCommentChecker: 0:00:00.455464 ms
stress constant evaluator: 0:00:00.810962 ms
write .dill: 0:00:01.040020 ms
print: 0:00:01.048330 ms
verify: 0:00:06.864096 ms
match expectations: 0:00:07.527595 ms
typeCheck: 0:00:12.512297 ms
outline: 0:04:31.713300 ms
```
The reason is that the outline also serializes the entire component (including the platform).
This CL disables that and instead gets (back) to:
With this CL:
```
$ out/ReleaseX64/dart pkg/front_end/test/fasta/outline_suite.dart --traceStepTiming
[...]
[ 01:15 | 100.0% | + 2914 | - 0 ]: outline/wildcard_variables/unnamed_optional_parameter_no_default
check errors: 0:00:00.347309 ms
ErrorCommentChecker: 0:00:00.438746 ms
stress constant evaluator: 0:00:00.915786 ms
write .dill: 0:00:01.092630 ms
print: 0:00:01.108090 ms
verify: 0:00:07.156487 ms
match expectations: 0:00:08.019510 ms
typeCheck: 0:00:14.013395 ms
outline: 0:00:41.738619 ms
```
Change-Id: I1fd7486384b34a54ec86b884f102eae6963508f3
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/372483
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.