| commit | 14889cc06d62f7c2941248960704db15be31bff0 | [log] [tgz] |
|---|---|---|
| author | Tess Strickland <sstrickl@google.com> | Wed Jun 11 04:43:24 2025 -0700 |
| committer | Tess Strickland <sstrickl@google.com> | Wed Jun 11 04:43:24 2025 -0700 |
| tree | bce401c8fac2b14e3a8c0a81a4bfbcbf4a69054b | |
| parent | b67482d6bc21fd7462c98122086eae56450d7d11 [diff] |
[vm] Handle Windows unwinding records better in the Mach-O loader. The Mach-O writer puts the unwinding records in a __unwind_info section, so just find the appropriate section and use its contents instead of forcing it to be at the end of the segment's memory space. Create an overload of UnwindingRecordsPlatform::RegisterExecutableMemory that takes a pointer to the start of the unwinding records for use by the Mach-O loader. Add __unwind_info for any executable segments that are not the text segment as well. Instead of testing host/target windows plus 64-bit arch, use the defines provided by platform/unwinding_records.h in the Mach-O writer and the ELF and Mach-O loaders. TEST=ci on Windows trybots Issue: https://github.com/dart-lang/sdk/issues/60307 Change-Id: Iee53c6725a681f44ac98ed9c9aecf1b75853ece5 Cq-Include-Trybots: luci.dart.try:vm-aot-linux-debug-x64-try,vm-mac-release-arm64-try,vm-aot-mac-release-arm64-try,vm-aot-mac-release-x64-try,vm-aot-dwarf-linux-product-x64-try,vm-linux-debug-x64-try,vm-mac-debug-arm64-try,vm-gcc-linux-try,vm-aot-win-release-arm64-try,vm-aot-win-release-x64-try,vm-win-release-x64-try,vm-win-release-arm64-try,vm-aot-win-debug-arm64-try,vm-win-debug-arm64-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/432960 Commit-Queue: Tess Strickland <sstrickl@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com> Reviewed-by: Slava Egorov <vegorov@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.