| commit | dfccc4a268c1a8fdc59152b6f8afd492d84ca31c | [log] [tgz] |
|---|---|---|
| author | Vyacheslav Egorov <vegorov@google.com> | Wed Sep 11 12:51:23 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 11 12:51:23 2024 +0000 |
| tree | 2bf14b64af7f3fe2fcd0b419bdc2dc88732be6cb | |
| parent | 0a4f390b7267cfb3beb5df48c7d14e38e22d3240 [diff] |
[vm/aot] Fix debug-info generation The algorithm for ordering sections in `CreateProgramTable` permitted skew between the order of sections in snapshot and corresponding debug info. This skew can lead to inconsistencies in `.text` section memory offset between two generated ELF files making debug info invalid. This skew was left unnoticed for a long time because executable segment has a huge alignment requirement (64K) while the effect of the skew was usually rather small and thus hidden by realignment. This CL adds a strict verification pass (always enabled) which guards against such skew in the future. A better architecture would be to ditch parallel generation of snapshot and corresponding ELF files altogether and other implement splitting as a post processing path over generated ELF or rely on external tooling. But this is a much bigger change than I am willing to invest time into right now. TEST=ci Cq-Include-Trybots: luci.dart.try:vm-aot-linux-product-x64-try,vm-aot-linux-debug-x64-try,vm-aot-linux-release-x64-try Change-Id: I0881783237faa6534eb3c076b6cae472bbdc7243 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/384742 Commit-Queue: Slava Egorov <vegorov@google.com> Reviewed-by: Martin Kustermann <kustermann@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.