commit | 4b7c6b1fa6e8fcb00e639c3ba545b390c2026c41 | [log] [tgz] |
---|---|---|
author | Jens Johansen <jensj@google.com> | Wed Nov 13 15:10:51 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 13 15:10:51 2024 +0000 |
tree | 65d8cf33ba6b71224e6069024c38a2c3fc0a6ec8 | |
parent | c1b7d34fb4624c4b775a37c5c47a2741cc292621 [diff] |
[parser] Remove (extension) Token.isA2 With 0ca1ff2281439684445a610fb737834e921fe7ac fixing the reason why we had `isA2` we can get rid of it. One 100-run-each-benchmark of compiling a fixed version of the CFE with the current version of the CFE I get ``` msec task-clock:u: -0.3133% +/- 0.2298% (-13.22 +/- 9.70) cycles:u: -0.4109% +/- 0.2303% (-71702583.62 +/- 40176749.86) instructions:u: -0.0150% +/- 0.0002% (-3206465.75 +/- 50567.00) branch-misses:u: -0.9597% +/- 0.8046% (-615355.48 +/- 515877.98) seconds time elapsed: -0.3138% +/- 0.2297% (-0.01 +/- 0.01) seconds user: -0.2991% +/- 0.2978% (-0.01 +/- 0.01) ``` (the only real thing to look at here is likely the `instructions:u` going down by ~3.2 mio.) For anyone interested: Manualy testing what 0ca1ff2281439684445a610fb737834e921fe7ac did vs the commit before (by running it 5 times each by hand through perf stat) I get instructions:u: -0.0831338% +/- 0.00115149% (-1.78503e+07 +/- 247246) (i.e. almost 18 mio less instructions). Change-Id: I01600c33364933da262b3354298255e8b2df8afb Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/394101 Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.