Roll BoringSSL from 380c17ad8fc2 to 514abb73bb80 (34 revisions)

https://boringssl.googlesource.com/boringssl.git/+log/380c17ad8fc2..514abb73bb80

2026-02-05 xfding@google.com Revert "Add support for ML-DSA `ctx` parameter. Add corresponding tests"
2026-02-05 rpolzer@google.com CI: also rename nosse2 to n2.
2026-02-05 rpolzer@google.com CI: move "fips" from short name into category, and rename "nosse2" to "n2".
2026-02-05 rpolzer@google.com Partial symbol prefixing support with delocate.
2026-02-04 rpolzer@google.com CI: build categories and short names in code.
2026-02-04 lizatretyakova@google.com Add support for ML-DSA `ctx` parameter. Add corresponding tests
2026-02-04 rpolzer@google.com CI: give linux32_nosse2_noasm the nosse2 short name.
2026-02-04 rpolzer@google.com Rebuild categories and short names for the BoringSSL CI console.
2026-02-04 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of EC_GROUP.
2026-02-04 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of EVP_PKEY.
2026-02-04 rpolzer@google.com Pregenerate: restructure console output.
2026-02-04 rpolzer@google.com Pregenerate: remove hack to find clang and to locate the Windows SDK.
2026-02-04 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of RSA.
2026-02-04 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of X509_STORE.
2026-02-04 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of EC_KEY.
2026-02-04 rpolzer@google.com New BCR release.
2026-02-04 rpolzer@google.com Delocate: also support `name = value` kind symbol aliasing.
2026-02-03 rpolzer@google.com Enable most of the prefixed builds that work.
2026-02-02 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of DSA.
2026-02-02 rpolzer@google.com Remove uses of `static inline` in C++.
2026-02-02 rpolzer@google.com Fix location of NASM flags.
2026-02-02 rpolzer@google.com Fix Clang-Tidy issues: missing includes.
2026-02-02 rpolzer@google.com MLDSA, MLKEM, SLHDSA: do not use extern "C" inside anon namespace.
2026-02-02 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of DH.
2026-02-02 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of BIO.
2026-02-02 rpolzer@google.com Also move most OPENSSL_free uses to Delete.
2026-02-02 xfding@google.com rust: Add RSA-PSS signature test
2026-02-02 rpolzer@google.com Remove non-namespaced symbols for ctor/dtor of CMS_ContentInfo and CMS_SignerInfo.
2026-02-02 rpolzer@google.com Replace malloc/sizeof pattern by New.
2026-02-02 rpolzer@google.com Add symbol prefixing validation to CMake.
2026-02-02 nfabritius@google.com Add support for RSA PSS.
2026-02-02 rpolzer@google.com Fix a broken Go doc comment.
2026-01-31 daniel@binaryparadox.net util/fipstools: add ACVP KTS-IFC crt support
2026-01-30 davidben@google.com Fix typo in 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@rotations.google.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@rotations.google.com
Change-Id: Icc9bdcbb087d23854390da993bc0750660933674
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/478720
Commit-Queue: Alexander Markov <alexmarkov@google.com>
Reviewed-by: Alexander Aprelev <aam@google.com>
Reviewed-by: Alexander Markov <alexmarkov@google.com>
1 file changed
tree: 628accfb3f821f40d2a9ae31e74cb23fee2f5c17
  1. .dart_tool/
  2. .github/
  3. benchmarks/
  4. build/
  5. docs/
  6. pkg/
  7. runtime/
  8. samples/
  9. sdk/
  10. tests/
  11. third_party/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitattributes
  16. .gitconfig
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .style.yapf
  21. AUTHORS
  22. BUILD.gn
  23. CHANGELOG.md
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. PATENT_GRANT
  30. PRESUBMIT.py
  31. pubspec.yaml
  32. README.dart-sdk
  33. README.md
  34. sdk.code-workspace
  35. sdk_args.gni
  36. sdk_packages.yaml
  37. SECURITY.md
  38. WATCHLISTS
README.md

Dart

An approachable, portable, and productive language for high-quality apps on any platform

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 platforms illustration

License & patents

Dart is free and open source.

See LICENSE and PATENT_GRANT.

Using Dart

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).

Building Dart

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.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

Roadmap

Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.