commit | c741d230ed73e57bf62b94ff118c4c9be6abe2fb | [log] [tgz] |
---|---|---|
author | DEPS Autoroller <dart-autoroll@skia-public.iam.gserviceaccount.com> | Thu Mar 27 08:07:17 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 27 08:07:17 2025 -0700 |
tree | 84deb7a1421eafbd0f6d8075e780db47ece6edb4 | |
parent | ca9a4dfbc700ea1fa7ee430244682699321712ea [diff] |
Roll BoringSSL from c6292fa69a65 to 02f0d8776ecd (19 revisions) https://boringssl.googlesource.com/boringssl.git/+log/c6292fa69a65..02f0d8776ecd 2025-03-24 davidben@google.com draft-kwiatkowski-tls-ecdhe-mlkem-01 is now draft-ietf-tls-ecdhe-mlkem-00 2025-03-22 davidben@google.com Remove MSVC C4702 suppressions in code 2025-03-21 davidben@google.com Remove MSVC warning suppressions around Windows system headers 2025-03-20 davidben@google.com Fix fuzzer build on Windows 2025-03-20 davidben@google.com Refresh fuzzer corpus 2025-03-20 davidben@google.com Simplfy fuzzer build 2025-03-20 bbe@google.com Make bcm use internal AES functions 2025-03-20 davidben@google.com Don't override the clock in BORINGSSL_UNSAFE_DETERMINISTIC_MODE 2025-03-20 davidben@google.com Fix the link order of various dependencies 2025-03-20 davidben@google.com Fix some duplicate #defines 2025-03-20 davidben@google.com Rewrite header guards 2025-03-19 ebiggers@google.com Remove the avx10_256 entry from BORINGSSL_function_hit 2025-03-19 ebiggers@google.com Clean up aes-gcm-avx512-x86_64.pl to assume 512-bit vectors 2025-03-19 ebiggers@google.com Rename avx10 and avx10_512 to avx512 2025-03-18 davidben@google.com delocate: Preserve AVX-512 tokens when rewriting labels 2025-03-18 bbe@google.com Tolerate RCS-MLS custom critical extensions 2025-03-18 bbe@google.com Accept only digital signature key usage for RCS-MLS 2025-03-18 bbe@google.com correct old license on aes.cc 2025-03-18 ebiggers@google.com Move gcm_gmult_vpclmulqdq_avx10 and add comment 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: Ic1b45e2ac4b4e49a194b5cb716adde2d92d94005 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/417621 Reviewed-by: Derek Xu <derekx@google.com> Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: 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 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.