Google Git
Sign in
pigweed / third_party / github / protocolbuffers / protobuf / 6245b7291ce99b861c4fb5e9ef09ddf85ff44a7a
commit6245b7291ce99b861c4fb5e9ef09ddf85ff44a7a[log] [tgz]
authorProtobuf Team Bot <protobuf-github-bot@google.com>Wed Oct 01 14:05:21 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Oct 01 14:09:36 2025 -0700
tree1c732d29356c50bcf42fbe0e1d1666d0d7e624c8
parent45f0eaa69473ac984e8f43b98ed22cfe9610d287 [diff]
Use the simplest possible implementation of encodeUtf8 instead of a fancy one that uses sun.misc.Unsafe.

Empirically in 2025 this appears to be faster than our implementation that tries to hand roll this and avoid a string copy and use sun.misc.Unsafe (and much faster in the case of ascii strings).

The JDK implementation is able to leverage the internal representation of the strings when encoding, including that it can have a very fast path for "internal representation is Latin1 and the string happens to be ascii, then it is already utf8". The exposed Java API unfortunately demands us have a temporary copied array here, but it empirically doesn't show up as a regression to have this shortlived object and copy.

This delta is only changing UnsafeProcessor path which is currently held back from Android, so its OK that this was only benchmarked on server and we don't need to worry about a regression on Android at this time.

PiperOrigin-RevId: 813904984
1 file changed
tree: 1c732d29356c50bcf42fbe0e1d1666d0d7e624c8
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. bazel/
  5. benchmarks/
  6. build_defs/
  7. ci/
  8. cmake/
  9. compatibility/
  10. conformance/
  11. csharp/
  12. docs/
  13. editions/
  14. editors/
  15. examples/
  16. go/
  17. hpb/
  18. hpb_generator/
  19. java/
  20. lua/
  21. objectivec/
  22. patches/
  23. php/
  24. pkg/
  25. python/
  26. ruby/
  27. rust/
  28. src/
  29. third_party/
  30. toolchain/
  31. upb/
  32. upb_generator/
  33. .bazelignore
  34. .bazeliskrc
  35. .bazelrc
  36. .clang-format
  37. .gitignore
  38. .gitmodules
  39. .readthedocs.yml
  40. appveyor.bat
  41. appveyor.yml
  42. BUILD.bazel
  43. Cargo.bazel.lock
  44. Cargo.lock
  45. CMakeLists.txt
  46. CODE_OF_CONDUCT.md
  47. CONTRIBUTING.md
  48. CONTRIBUTORS.txt
  49. Disable_bundle_install.patch
  50. fix_permissions.sh
  51. generate_descriptor_proto.sh
  52. global.json
  53. google3_export_generated_files.sh
  54. LICENSE
  55. maven_dev_install.json
  56. maven_install.json
  57. MODULE.bazel
  58. Neverlink_jruby_jars.patch
  59. PrivacyInfo.xcprivacy
  60. protobuf.bzl
  61. Protobuf.podspec
  62. protobuf_deps.bzl
  63. protobuf_release.bzl
  64. protobuf_version.bzl
  65. README.md
  66. regenerate_stale_files.sh
  67. SECURITY.md
  68. version.json
  69. WORKSPACE
  70. WORKSPACE.bzlmod
README.md

Protocol Buffers - Google's data interchange format

OpenSSF Scorecard

Copyright 2023 Google LLC

Overview

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can learn more about it in protobuf's documentation.

This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.

Working With Protobuf Source Code

Most users will find working from supported releases to be the easiest path.

If you choose to work from the head revision of the main branch your build will occasionally be broken by source-incompatible changes and insufficiently-tested (and therefore broken) behavior.

If you are using C++ or otherwise need to build protobuf from source as a part of your project, you should pin to a release commit on a release branch.

This is because even release branches can experience some instability in between release commits.

Bazel with Bzlmod

Protobuf supports Bzlmod with Bazel 7 +. Users should specify a dependency on protobuf in their MODULE.bazel file as follows.

bazel_dep(name = "protobuf", version = <VERSION>)

Users can optionally override the repo name, such as for compatibility with WORKSPACE.

bazel_dep(name = "protobuf", version = <VERSION>, repo_name = "com_google_protobuf")

Bazel with WORKSPACE

Users can also add the following to their legacy WORKSPACE file.

Note that with the release of 30.x there are a few more load statements to properly set up rules_java and rules_python.

http_archive(
    name = "com_google_protobuf",
    strip_prefix = "protobuf-VERSION",
    sha256 = ...,
    url = ...,
)

load("@com_google_protobuf//:protobuf_deps.bzl", "protobuf_deps")

protobuf_deps()

load("@rules_java//java:rules_java_deps.bzl", "rules_java_dependencies")

rules_java_dependencies()

load("@rules_java//java:repositories.bzl", "rules_java_toolchains")

rules_java_toolchains()

load("@rules_python//python:repositories.bzl", "py_repositories")

py_repositories()

Protobuf Compiler Installation

The protobuf compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.

For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our GitHub release page.

In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.

If you are looking for an old version that is not available in the release page, check out the Maven repository.

These pre-built binaries are only provided for released versions. If you want to use the github main version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.

If you would like to build protoc binary from source, see the C++ Installation Instructions.

Protobuf Runtime Installation

Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:

LanguageSource
C++ (include C++ runtime and protoc)src
Javajava
Pythonpython
Objective-Cobjectivec
C#csharp
Rubyruby
Goprotocolbuffers/protobuf-go
PHPphp
Dartdart-lang/protobuf
JavaScriptprotocolbuffers/protobuf-javascript

Quick Start

The best way to learn how to use protobuf is to follow the tutorials in our developer guide.

If you want to learn from code examples, take a look at the examples in the examples directory.

Documentation

The complete documentation is available at the Protocol Buffers doc site.

Support Policy

Read about our version support policy to stay current on support timeframes for the language libraries.

Developer Community

To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.