[vm] Update assembler to access AbstractType::flags_ as Uint32. In d592882f, the old uint8_t `type_state_` and `nullability_` fields in subclasses of `AbstractType` were merged into a single uint32_t `flags_` field in `AbstractType` itself. Accessing the nullability information was abstracted into two methods: * `LoadAbstractTypeNullability` * `CompareAbstractTypeNullabilityWith` However, the code from these methods were based off the old `CompareTypeNullabilityWith` and `CompareFunctionTypeNullabilityWith` methods that used unsigned byte loads to access the old field, and kept that even though the new field is now a 32-bit unsigned integer. This works for now, because the nullability portion of the `flags_` field happens to be the lowest two bits, but might lead to confusion if someone attempts to write similar code for accessing the other parts of the `flags_` field without realizing it's larger than 8 bits. Thus, this CL does the following: * Unifies the implementation of both methods across architectures. * Adds a native slot definition for the `AbstractType::flags_` field and uses `LoadFromSlot` to load the `flags_` field instead. Other places where the `AbstractType::flags_` field is accessed from the assembler are also changed to use `LoadFromSlot` appropriately. TEST=The existing suite of tests are sufficient. Change-Id: Ie578e4dddce810223ca9e767403136cb40d340f3 Cq-Include-Trybots: luci.dart.try:vm-aot-linux-release-x64-try,vm-aot-linux-release-simarm_x64-try,vm-aot-linux-release-simarm64-try,vm-aot-linux-debug-simarm_x64-try,vm-aot-linux-debug-simriscv64-try,vm-aot-mac-release-arm64-try,vm-aot-mac-release-x64-try,vm-aot-linux-debug-x64c-try,vm-kernel-precomp-linux-release-simarm-try,vm-linux-release-x64-try,vm-linux-release-simarm64-try,vm-linux-release-simarm-try,vm-linux-release-ia32-try,vm-linux-debug-simriscv64-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/302187 Reviewed-by: Daco Harkes <dacoharkes@google.com> Commit-Queue: Tess Strickland <sstrickl@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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.