Roll BoringSSL from 5d4b8d99a14a to 55de8cd4a040 (23 revisions) https://boringssl.googlesource.com/boringssl.git/+log/5d4b8d99a14a..55de8cd4a040 2025-03-14 leonardchan@google.com [fuzz] Replace is_pod 2025-03-12 agl@chromium.org Handle nullptr arguments to FIPS key generation functions 2025-03-12 davidben@google.com Move some exponentation functions out of the FIPS module 2025-03-12 davidben@google.com Remove optimized even modulus mod-exp implementation 2025-03-12 davidben@google.com Warn in SSL_export_keying_material API docs that lengths must match 2025-03-11 bbe@google.com Add mode for MLS client auth, with EKU checking 2025-03-11 davidben@google.com Const-correct SSL_export_keying_material 2025-03-11 davidben@google.com Remove unused "endbranch" x86-64 encoder 2025-03-11 ambrosin@google.com Add AES-EAX EVP_AEAD cipher 2025-03-11 davidben@google.com Stop manually encoding a bunch of x86-64 instructions 2025-03-11 davidben@google.com Migrate remaining uses of io/ioutil 2025-03-11 davidben@google.com go mod tidy 2025-03-11 davidben@google.com acvptool: Disable GCS support by default 2025-03-11 davidben@google.com Update deps and tag a version for BCR 2025-03-11 davidben@google.com Replace an old README.chromium file with a plain README.md 2025-03-11 davidben@google.com Implement draft-ietf-tls-cross-sni-resumption 2025-03-10 ebiggers@google.com Fix missing vzeroupper in poly_Rq_mul() 2025-03-10 ebiggers@google.com Use vmovdqa to save/restore xmm registers in AES-GCM code on Windows 2025-03-10 ebiggers@google.com Fix missing vzeroupper in gcm_ghash_vpclmulqdq_avx2() for len=16 2025-03-10 ebiggers@google.com aes-gcm-avx10-x86_64.pl: use strict mode and sync with avx2 code 2025-03-10 agl@imperialviolet.org Update PQ ACVP to reflect NIST's breaking changes. 2025-03-10 ebiggers@google.com aes-gcm-avx10-x86_64.pl: fold _ghash_mul_step into _ghash_mul 2025-03-10 davidben@google.com runner: Test export keying material across all protocols 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: Ib5508c914fb2ce9fbcf741888ad4511a60fcc1df Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/415685 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Alexander Markov <alexmarkov@google.com> Reviewed-by: 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.