1. 18 Mar, 2016 1 commit
  2. 17 Mar, 2016 2 commits
    • Thomas Van Lenten's avatar
      Merge pull request #1325 from thomasvl/shrink_overhead · 5e933847
      Thomas Van Lenten authored
      Shrink ObjC overhead (generated size and some runtime sizes)
      5e933847
    • Thomas Van Lenten's avatar
      Shrink ObjC overhead (generated size and some runtime sizes) · 79a23c43
      Thomas Van Lenten authored
      NOTE: This is a binary breaking change as structure sizes have changed size
      and/or order.
      
      - Drop capturing field options, no other options were captured and other mobile
        targeted languages don't try to capture this sort information (saved 8
        bytes for every field defined (in static data and again in field descriptor
        instance size data).
      - No longer generate/compile in the messages/enums in descriptor.proto. If
        developers need it, they should generate it and compile it in. Reduced the
        overhead of the core library.
      - Compute the number of has_bits actually needs to avoid over reserving.
      - Let the boolean single fields store via a has_bit to avoid storage, makes
        the common cases of the instance size smaller.
      - Reorder some flags and down size the enums to contain the bits needed.
      - Reorder the items in the structures to manually ensure they are are packed
        better (especially when generating 64bit code - 8 bytes for every field,
        16 bytes for every extension, instance sizes 8 bytes also).
      - Split off the structure initialization so when the default is zero, the
        generated static storage doesn't need to reserve the space. This is batched
        at the message level, so all the fields for the message have to have zero
        defaults to get the saves. By definition all proto3 syntax  files fall into
        this case but it also saves space for the proto2 that use the standard
        defaults. (saves 8 bytes of static data for every field that had a zero
        default)
      - Don't track the enums defined by a message. Nothing in the runtime needs it
        and it was just generation and runtime overhead. (saves 8 bytes per enum)
      - Ensure EnumDescriptors are started up threadsafe in all cases.
      - Split some of the Descriptor initialization into multiple methods so the
        generated code isn't padded with lots of zero/nil args.
      - Change how oneof info is feed to the runtime enabling us to generate less
        static data (8 bytes saved per oneof for 64bit).
      - Change how enum value informat is capture to pack the data and only decode
        it if it ends up being needed. Avoids padding issues causing bloat of 64bit,
        and removes the needs for extra pointers in addition to the data (just the
        data and one pointer now).
      79a23c43
  3. 14 Mar, 2016 2 commits
  4. 12 Mar, 2016 3 commits
  5. 11 Mar, 2016 2 commits
  6. 10 Mar, 2016 1 commit
  7. 09 Mar, 2016 2 commits
  8. 08 Mar, 2016 5 commits
  9. 07 Mar, 2016 5 commits
  10. 05 Mar, 2016 4 commits
    • Joshua Haberman's avatar
      Merge pull request #1298 from craigcitro/fix_setup · 9242d9b7
      Joshua Haberman authored
      Add back the namespace_packages arg in setup.py.
      9242d9b7
    • Antal Tátrai's avatar
      3cc35adb
    • Craig Citro's avatar
      Add back the namespace_packages arg in setup.py. · 0e7c0c2f
      Craig Citro authored
      Improves #1296.
      
      The problem: in the previous patch, we tweaked the __init__.py files to use
      namespaces, but no longer declared ourselves as a namespace package. The
      second half was unwise.
      
      Note that this only comes up when installing protobuf alongside another
      package that also installs into the google namespace; as of right now, the
      only PyPI package that does is googleapis-common-protos, though the GAE SDK
      also uses google.appengine. Installing either or both of those alongside this
      package now works.
      
      The case that still remains is the upgrade path, which is also what worried me
      in #713. It seems that if protobuf 2.6.1 is installed, there's no way to
      safely upgrade that to work with a newer protobuf. However, `pip uninstall` &&
      `pip install` does the trick.
      0e7c0c2f
    • Joshua Haberman's avatar
      Merge pull request #1139 from haberman/rubyjsoncamel · e70f9256
      Joshua Haberman authored
      Changed Ruby to properly camelCase its JSON by default.
      e70f9256
  11. 04 Mar, 2016 2 commits
  12. 03 Mar, 2016 2 commits
  13. 02 Mar, 2016 1 commit
  14. 01 Mar, 2016 2 commits
  15. 29 Feb, 2016 3 commits
  16. 25 Feb, 2016 3 commits
    • Jisi Liu's avatar
      Merge pull request #1233 from davidzchen/python-path · 60a0d41a
      Jisi Liu authored
      Remove hack for building Python support with Bazel.
      60a0d41a
    • David Z. Chen's avatar
      Remove hack for building Python support with Bazel. · 985c9684
      David Z. Chen authored
      This change makes use of new imports attribute for Bazel's Python rules, which
      enable adding directories to the PYTHONPATH. This allows us to remove
      the hack for building protobuf's Python support with Bazel and now
      allows projects to include protobuf using a Bazel external repository
      rather than requiring it to be imported directly into the source tree as
      //google/protobuf.
      
      This change also updates the protobuf BUILD file to use a named
      repository, @python//, for including Python headers rather than
      //util/python. This allows projects to specify their own package for
      Python headers when including protobuf with an external repository.
      
      Fixes #1230
      985c9684
    • Jisi Liu's avatar
      Merge pull request #1275 from keveman/grpc_support · fb714b36
      Jisi Liu authored
      Fixed grpc C++ plugin support.
      fb714b36