Branch-free varint size calculation. On android art, compiles to:

```
int com.google.android.test.Outer.computeUInt32SizeNoTag(int) [24 bytes]
    0x000024d0    mov w0, #0x160
    0x000024d4    clz w1, w1
    0x000024d8    add w1, w1, w1, lsl #3
    0x000024dc    sub w0, w0, w1
    0x000024e0    lsr w0, w0, #6
    0x000024e4    ret
```
versus existing:
```
int com.google.android.test.Outer.computeUInt32SizeNoTag(int) [72 bytes]
    0x000022a0    and w0, w1, #0xffffff80
    0x000022a4    cbnz w0, #+0xc (addr 0x22b0)
    0x000022a8    mov w0, #0x1
    0x000022ac    b #+0x38 (addr 0x22e4)
    0x000022b0    and w0, w1, #0xffffc000
    0x000022b4    cbnz w0, #+0xc (addr 0x22c0)
    0x000022b8    mov w0, #0x2
    0x000022bc    b #+0x28 (addr 0x22e4)
    0x000022c0    and w0, w1, #0xffe00000
    0x000022c4    cbnz w0, #+0xc (addr 0x22d0)
    0x000022c8    mov w0, #0x3
    0x000022cc    b #+0x18 (addr 0x22e4)
    0x000022d0    mov w2, #0x5
    0x000022d4    mov w0, #0x4
    0x000022d8    and w1, w1, #0xf0000000
    0x000022dc    cmp w1, #0x0 (0)
    0x000022e0    csel w0, w2, w0, ne
    0x000022e4    ret
```

PiperOrigin-RevId: 591113652
2 files changed
tree: c15e08b815750706ec6bfbf6938a4107d56d28b7
  1. .github/
  2. bazel/
  3. benchmarks/
  4. build_defs/
  5. ci/
  6. cmake/
  7. conformance/
  8. csharp/
  9. docs/
  10. editors/
  11. examples/
  12. java/
  13. lua/
  14. objectivec/
  15. php/
  16. pkg/
  17. protos/
  18. protos_generator/
  19. python/
  20. ruby/
  21. rust/
  22. src/
  23. third_party/
  24. toolchain/
  25. upb/
  26. upb_generator/
  27. .bazelignore
  28. .bazelrc
  29. .clang-format
  30. .gitignore
  31. .gitmodules
  32. .readthedocs.yml
  33. appveyor.bat
  34. appveyor.yml
  35. BUILD.bazel
  36. Cargo.bazel.lock
  37. Cargo.lock
  38. CMakeLists.txt
  39. CODE_OF_CONDUCT.md
  40. CONTRIBUTING.md
  41. CONTRIBUTORS.txt
  42. fix_permissions.sh
  43. generate_descriptor_proto.sh
  44. global.json
  45. google3_export_generated_files.sh
  46. LICENSE
  47. maven_install.json
  48. MODULE.bazel
  49. Protobuf-C++.podspec
  50. protobuf.bzl
  51. Protobuf.podspec
  52. protobuf_deps.bzl
  53. protobuf_release.bzl
  54. protobuf_version.bzl
  55. README.md
  56. regenerate_stale_files.sh
  57. SECURITY.md
  58. version.json
  59. WORKSPACE
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.

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.