Use _upb_Message_AlignedMemsetZero in upb_Message_Clear `upb_Message_Clear` zeroed the message with a `memset` library call. Use the same inline aligned zeroing as `_upb_Message_New` instead (message sizes are multiples of kUpb_Message_Align, and messages are always kUpb_Message_Align-aligned). Also stop resetting the size of the message's internal data (unknown fields and extensions) after clearing: the internal data pointer is in the message header, which the clear zeroes, so nothing refers to that internal data afterwards and the store was dead. (Copies never share internal data: upb_Message_ShallowCopy gives the copy its own.) This saves loading the header before the clear. android_arm64 (-c opt, fasttable), upb_Message_DeepCopy (which inlines upb_Message_Clear), before: stp x30, x23, [sp, #-0x30]! stp x22, x21, [sp, #0x10] stp x20, x19, [sp, #0x20] mov x20, x2 ldr x8, [x0] ldrh w2, [x2, #0x8] mov x21, x1 mov w1, wzr mov x19, x3 mov x22, x0 and x23, x8, #0xfffffffffffffffe bl memset cbz x23, 1f str wzr, [x23] 1:mov x0, x22 mov x1, x21 mov x2, x20 mov x3, x19 bl _upb_Message_Copy ldp x20, x19, [sp, #0x20] cmp x0, #0x0 ldp x22, x21, [sp, #0x10] cset w0, ne ldp x30, x23, [sp], #0x30 ret after (no call, so no callee-saved registers to spill around it, and no load and store of the internal data): str x30, [sp, #-0x10]! ldrh w8, [x2, #0x8] mov x9, x0 add x10, x0, x8 str xzr, [x9] cmp x8, #0x8 b.eq 2f 1:stp xzr, xzr, [x9], #0x10 stp xzr, xzr, [x10, #-0x10]! cmp x9, x10 b.lo 1b 2:bl _upb_Message_Copy cmp x0, #0x0 cset w0, ne ldr x30, [sp], #0x10 ret The error path of `_upb_Message_Copy`, which clears `dst`, likewise replaces its `memset` call with the inline loop. No other function in the upb message, wire and decode_fast objects changes. PiperOrigin-RevId: 998754226
Copyright 2008 Google LLC
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.
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.
Protobuf supports Bzlmod with Bazel 8 +. 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")
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()
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 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:
| Language | Source |
|---|---|
| C++ (include C++ runtime and protoc) | src |
| Java | java |
| Python | python |
| Objective-C | objectivec |
| C# | csharp |
| Ruby | ruby |
| Go | protocolbuffers/protobuf-go |
| PHP | php |
| Dart | dart-lang/protobuf |
| JavaScript | protocolbuffers/protobuf-javascript |
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.
The complete documentation is available at the Protocol Buffers doc site.
Read about our version support policy to stay current on support timeframes for the language libraries.
To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.