[vm/compiler] Add the capability for Slots on non-Dart objects. Now Slots have an extra flag that describes whether or not the instance object for that Slot is tagged (Dart objects) or untagged (non-Dart objects like Thread). Add new Slot categories for Slots with untagged instances, based on the return value of the Slot: * a tagged value (e.g., the finalizers_ field of Isolate), * an untagged value (e.g., the isolate_ field of Thread), or * an unboxed value (e.g., the enabled_ field of StreamInfo). The primary difference in the specification of slots for untagged instances vs tagged instances is that the slots for untagged instances do not include an underlying type (as only Dart objects have an Untagged<X> for each <X> class that specifies the actual object layout). Also do a little more refactoring of Slot categories to simplify some switch statements that now only need to be updated if the categories the switch statement deals with change. For example, methods for range analysis are only interested in Slots that are guaranteed to contain integers, so now those methods are written in a way that they only need to be updated if a new tagged integer Slot declaration is added. Adjust LoadFromSlot, StoreToSlot, and StoreToSlotNoBarrier to appropriately handle Slots on untagged instances, and change LoadField and StoreField's RequiredInputRepresentation methods to appropriately returned kTagged or kUntagged based on the slot. TEST=ci Cq-Include-Trybots: luci.dart.try:vm-aot-android-release-arm64c-try,vm-aot-android-release-arm_x64-try,vm-aot-linux-debug-x64-try,vm-aot-linux-debug-x64c-try,vm-aot-mac-release-arm64-try,vm-aot-mac-release-x64-try,vm-aot-obfuscate-linux-release-x64-try,vm-aot-optimization-level-linux-release-x64-try,vm-appjit-linux-debug-x64-try,vm-asan-linux-release-x64-try,vm-checked-mac-release-arm64-try,vm-eager-optimization-linux-release-ia32-try,vm-eager-optimization-linux-release-x64-try,vm-ffi-android-debug-arm-try,vm-ffi-android-debug-arm64c-try,vm-ffi-qemu-linux-release-arm-try,vm-ffi-qemu-linux-release-riscv64-try,vm-linux-debug-ia32-try,vm-linux-debug-x64c-try,vm-mac-debug-arm64-try,vm-mac-debug-x64-try,vm-msan-linux-release-x64-try,vm-reload-linux-debug-x64-try,vm-reload-rollback-linux-debug-x64-try,vm-ubsan-linux-release-x64-try,vm-win-debug-arm64-try,vm-win-debug-x64-try,vm-win-release-ia32-try Change-Id: Ic27de4f092c9e087486066459f68a82b4e1685b0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/357341 Commit-Queue: Tess Strickland <sstrickl@google.com> Reviewed-by: Daco Harkes <dacoharkes@google.com> Reviewed-by: Alexander Markov <alexmarkov@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 on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.