commit | 38680a7c29595c8df944bbe351b7a9f1bd5151c4 | [log] [tgz] |
---|---|---|
author | Tess Strickland <sstrickl@google.com> | Thu May 30 09:33:29 2024 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 30 09:33:29 2024 +0000 |
tree | f4b4e8b756fe405850d822940857a7a585321061 | |
parent | 9a9b33eb0b950dec7524274e1eb06beb2e7ff020 [diff] |
[vm] Avoid truncated initial definitions in FlowGraphPrinter. FlowGraphPrinter::PrintOneInstruction uses a stack-allocated statically-sized buffer to print the instruction. If the instruction is a block entry with initial definitions, then that buffer would need to be large enough to hold the printed information for the block entry and all of its initial definitions. However, in some pathological cases, like the Dart fuzzer, graphs are created where the initial definitions can end up truncated due to the use of a large number of constants. Instead, add the following protected methods to BlockEntryWithInitialDefs: * PrintBlockHeaderTo, a pure virtual method that specifies how to print the block header information, overridden in each subclass. * PrintInitialDefinitionsTo, a non-virtual method that prints the initial definitions. It takes an additional argument, a callback which takes the buffer being used for printing, and invokes the callback after printing each initial definition. Also adds BlockEntryWithInitialDefs::PrintTo, which calls PrintBlockHeaderTo and PrintInitialDefinitionsTo in sequence, providing a no-op callback to the latter, and removes the PrintTo overrides in the subclasses in favor of this base implementation. Adjusts FlowGraphPrinter::PrintOneInstruction to call PrintBlockHeaderTo and PrintInitialDefinitionsTo for BlockEntryWithInitialDefs instructions, providing a callback that prints the current contents of the buffer and then clears it. With this, it is unlikely using a statically-sized stack-allocated buffer as an intermediate will cause truncation, as each initial definition usually fits on a single line. TEST=ci (internal debugging-only output, tested manually) Issue: https://github.com/dart-lang/sdk/issues/55864 Change-Id: I7a7919cd6d76a22e018603240fe0ba6a09c2e6d3 Cq-Include-Trybots: luci.dart.try:vm-aot-mac-release-arm64-try,vm-aot-linux-debug-simarm_x64-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/368580 Reviewed-by: Martin Kustermann <kustermann@google.com> Commit-Queue: Tess Strickland <sstrickl@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.