Protobuf: Move thread-local global data to globals.cc

This CL is a followup to https://codereview.chromium.org/2756543002/ which moved
all variables in .data and .bss into globals.cc.  However, I overlooked thread-local
variables in .tdata and .tbss.  This CL moves those too.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_dbg_ng;master.tryserver.chromium.mac:mac_chromium_dbg_ng;master.tryserver.chromium.win:win_chromium_dbg_ng
R=pkasting@chromium.org
CC=piman@chromium.org
BUG=703706

Review-Url: https://codereview.chromium.org/2759423004
Cr-Original-Commit-Position: refs/heads/master@{#458677}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 57c80c99d9f3355e5dc1829d0ac2eeffe7cd26b6
6 files changed
tree: b31378333c40dc6e23a41ac3145ef8620db06b47
  1. benchmarks/
  2. cmake/
  3. conformance/
  4. csharp/
  5. docs/
  6. editors/
  7. examples/
  8. java/
  9. javanano/
  10. jenkins/
  11. js/
  12. m4/
  13. objectivec/
  14. patches/
  15. php/
  16. protoc-artifacts/
  17. python/
  18. ruby/
  19. src/
  20. third_party/
  21. util/
  22. .gitignore
  23. .travis.yml
  24. __init__.py
  25. appveyor.bat
  26. appveyor.yml
  27. autogen.sh
  28. BUILD
  29. BUILD.gn
  30. CHANGES.txt
  31. configure.ac
  32. CONTRIBUTORS.txt
  33. DEPS
  34. generate_descriptor_proto.sh
  35. gmock.BUILD
  36. LICENSE
  37. Makefile.am
  38. OWNERS
  39. post_process_dist.sh
  40. proto_library.gni
  41. protobuf-lite.pc.in
  42. protobuf.bzl
  43. protobuf.pc.in
  44. Protobuf.podspec
  45. README.chromium
  46. README.md
  47. six.BUILD
  48. tests.sh
  49. update_file_lists.sh
  50. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

Build Status Build status

Copyright 2008 Google Inc.

https://developers.google.com/protocol-buffers/

Overview

Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can find protobuf's documentation on the Google Developers site.

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.

Protocol Compiler Installation

The protocol 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 release page:

https://github.com/google/protobuf/releases

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 repo here:

http://repo1.maven.org/maven2/com/google/protobuf/protoc/

These pre-built binaries are only provided for released versions. If you want to use the github master 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
JavaNanojavanano
JavaScriptjs
Rubyruby
Gogolang/protobuf
PHPTBD

Usage

The complete documentation for Protocol Buffers is available via the web at:

https://developers.google.com/protocol-buffers/