| commit | 0dc86856cad68edec516d14d1853e2aa78632718 | [log] [tgz] |
|---|---|---|
| author | Tess Strickland <sstrickl@google.com> | Wed Nov 01 12:47:59 2023 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 01 12:47:59 2023 +0000 |
| tree | e16337cf8c4779b69daf454abf917e0d5c700d91 | |
| parent | 3a6daede9a8533571bf088915784d5af93b24f88 [diff] |
Reland "[vm/compiler] Consistently use PointerBase.data values as FFiIntPtr." This is a reland of commit 60d1a40462e0b489a68e9f7a1fe159e9edac19be Original change's description: > Reland "[vm/compiler] Consistently use PointerBase.data values as FFiIntPtr." > > This is a reland of commit 5c4fd506676ced39567c0383b1bb643668eb0222 > > The range analysis change was replaced with a different change, > on which this CL is based. In addition, another preceding CL > unified a few methods on subclasses of UnboxIntegerOpInstr, because > the inconsistencies between UnboxInt32OpInstr and UnboxUint32OpInstr > and how unboxed int32 vs. uint32 constants were handled caused the > issue seen after landing the original CL. > > Thus, this CL is purely changes of kUnboxedIntPtr to kUnboxedFfiIntPtr > when appropriate plus test changes. > > TEST=vm/dart/regress_306327173_il_test > vm/dart/address_local_pointer_il_test > > Original change's description: > > [vm/compiler] Consistently use PointerBase.data values as FFiIntPtr. > > > > Also if converting an unboxed int with only non-negative values > > that fit in 32 bits to a uint32, then keep the range from the value. > > > > TEST=regress_306327173_il_test > > > > Cq-Include-Trybots: luci.dart.try:vm-aot-linux-debug-simarm_x64-try,vm-aot-linux-release-x64-try,vm-aot-linux-debug-x64-try,vm-aot-linux-debug-x64c-try > > Change-Id: Id9e7c2d5f477e560822a02574739c57d77b5a6d1 > > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/332202 > > Reviewed-by: Daco Harkes <dacoharkes@google.com> > > Reviewed-by: Slava Egorov <vegorov@google.com> > > Commit-Queue: Tess Strickland <sstrickl@google.com> > > Change-Id: I1f66bc9d1ca7569c913f02b611b4a27f189605ac > Cq-Include-Trybots: luci.dart.try:vm-aot-linux-debug-simarm_x64-try,vm-aot-linux-release-x64-try,vm-aot-linux-debug-x64-try,vm-aot-linux-debug-x64c-try,vm-ffi-qemu-linux-release-arm-try,vm-ffi-android-release-arm-try > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/332340 > Reviewed-by: Daco Harkes <dacoharkes@google.com> > Commit-Queue: Tess Strickland <sstrickl@google.com> TEST=vm/dart/regress_306327173_il_test vm/dart/address_local_pointer_il_test Change-Id: I8f789847670c66a823cbbc6dca5b74a8b7a2cd88 Cq-Include-Trybots: luci.dart.try:vm-aot-linux-debug-simarm_x64-try,vm-aot-linux-release-x64-try,vm-aot-linux-debug-x64-try,vm-aot-linux-debug-x64c-try,vm-ffi-qemu-linux-release-arm-try,vm-ffi-android-release-arm-try,vm-linux-release-simarm-try Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/333002 Reviewed-by: Daco Harkes <dacoharkes@google.com> Commit-Queue: Tess Strickland <sstrickl@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.