| commit | 68e917c116e493aed74f1fda16ee715e8ec53b03 | [log] [tgz] |
|---|---|---|
| author | DEPS Autoroller <dart-autoroll@skia-public.iam.gserviceaccount.com> | Mon May 12 10:53:09 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 12 10:53:09 2025 -0700 |
| tree | d0dfaadb361dc30699144d98808df10390eef1ae | |
| parent | eb563faf6dd8f2f4e252c4ced3d790a4945ea689 [diff] |
Roll BoringSSL from a70ec8dd2cc1 to 45cab558a838 (19 revisions) https://boringssl.googlesource.com/boringssl.git/+log/a70ec8dd2cc1..45cab558a838 2025-05-09 davidben@google.com Send only usable trust anchor IDs in EncryptedExtensions 2025-05-09 davidben@google.com Add CBB_discard 2025-05-08 davidben@google.com Document that "add1" is like "set1" 2025-05-08 davidben@google.com Remove ext_dat.h 2025-05-08 davidben@google.com Remove v3_ocsp_accresp 2025-05-07 davidben@google.com Don't stack-allocate incomplete X509/X509_CRL objects 2025-05-07 davidben@google.com Also add BIO_meth_get_write and BIO_meth_get_read 2025-05-07 davidben@google.com Reapply "Remove Karatsuba multiplication in BIGNUM" 2025-05-07 davidben@google.com Test non-NEON codepaths with a OPENSSL_NO_STATIC_NEON_FOR_TESTING 2025-05-07 davidben@google.com Simplify the implementation of OPENSSL_STATIC_ARMCAP 2025-05-02 davidben@google.com Use C++ destructors a little more 2025-05-02 davidben@google.com Clean up ssl_file.cc 2025-05-02 davidben@google.com Remove some dead code from SSL_CTX_use_certificate_chain_file 2025-05-02 davidben@google.com Write some tests for ssl_file.cc 2025-05-02 gavinmak@google.com Remove --no_auth from download_from_google_storage hooks 2025-05-01 davidben@google.com Rewrite crypto_md32_* with templates instead of function pointers 2025-05-01 davidben@google.com Convert EC_KEY_derive_from_secret to scopers 2025-05-01 davidben@google.com Add various missing includes 2025-04-30 davidben@google.com delocate: Support more aarch64 load instructions with :lo12: If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/boringssl-dart-sdk Please CC dart-engprod@google.com,dart-vm-gardener@grotations.appspotmail.com,dart-vm-team@google.com on the revert to ensure that a human is aware of the problem. To file a bug in BoringSSL: https://crbug.com/boringssl/new To file a bug in Dart SDK: https://github.com/dart-lang/sdk/issues To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: dart-vm-gardener@grotations.appspotmail.com Change-Id: Ie56067d5e51acfcb9107e9de5720c21a188b6dfc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/427641 Reviewed-by: Alexander Aprelev <aam@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com> Commit-Queue: Alexander Aprelev <aam@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.