* commit '8a9fc09c92cf0b1f08186c9339952e47eddee74b':
  Revert "Don't reset cachedSize to 0 in getSerializedSize"

* commit 'ce2f59915e0b41c935e3f72a2b7b71b6c19b6860':
  Revert "Don't reset cachedSize to 0 in getSerializedSize"

This reverts commit c6e12c6702ca764486f952654ba1568f00efe813.

This reverts commit f213b0c6a86503ad752139f04f343578df45db07, reversing
changes made to 1a4b1d52e44104f2e10d0cdc585dde88602843d2.

* commit '5b931dc798d882754f3e7a876fc6d820fa371e95':
  Don't reset cachedSize to 0 in getSerializedSize

* commit 'ec0b12c34a6329d2f98003e9102fe2d75726c797':
  Don't reset cachedSize to 0 in getSerializedSize

This avoids a race-condition when cachedSize is momentarily set to 0
for non-empty messages if multiple threads call getSerializedSize
(e.g. during serialization).

Change-Id: I15a8ded92edbf41bf1c8d787960c5bbbc8a323c5

* commit '0031029939c440e42e8e43cea3401f135c1af7d6':
  Fix compile error on mac 10.9

* commit '51ef8f39de376fe71ce5d2c682abe4f974cf8074':
  Fix compile error on mac 10.9

* commit '214997cefa5554c3670ea76293bbf751111704e4':
  Extension overhaul.

* commit 'afc1553a9eb56eff742828c9c819eafa363cdcc9':
  Extension overhaul.

* commit '5d33d23ded77a145f59a915f19044aa14335d93b':
  Fix repeated packed field merging code for non-packed data.
  Add validation when parsing enum fields.

* commit '447f664aef6694bb9fb3db85d6166d908cde8a8d':
  Fix repeated packed field merging code for non-packed data.
  Add validation when parsing enum fields.

* changes:
  Fix repeated packed field merging code for non-packed data.
  Add validation when parsing enum fields.

Enum fix is already included in the previous commit.

Bug: https://code.google.com/p/android/issues/detail?id=64893
Change-Id: I9fecff3c8822918a019028eb57fa39b361a2c960

Invalid values from the wire are silently ignored.
Unlike full/lite, the invalid values are not stored into the
unknown fields, because there's no way to get them out from
Nano's unknown fields without a matching Extension.

Edited README and slightly moved it towards a standalone
section for Nano, independent of the Micro section.

Change-Id: I2c1eb07f4d6d8f3aea242b8ddd95b9c966f3f177

* commit 'd5219df3ce036d4f43262bbda1016097a59a0c81':
  Allow whitespace in nano codegen options.

* commit 'a8af729b5ef822971f025a7e8ff197545986910d':
  Allow whitespace in nano codegen options.

So we don't need to keep all option in a single line in the .mk files.

Change-Id: I786b879b334cac4cd13b32fabcb76efe53b4ac80

* commit '1be96c579a34924bd20f19a0911b101ade08b0f3':
  Correctness: floating point equality using bits instead of ==.

* commit '538abc5b6514460fce1e72da9f49591c6d4ba2e0':
  Don't serialize required fields whose 'has' flags are unset.

* commit '4b5874fad099faefb469c632e4c7b854cea733ae':
  Correctness: floating point equality using bits instead of ==.

* commit 'd6aeae143cde31b79a2d57a3ee0e41d9083d232d':
  Don't serialize required fields whose 'has' flags are unset.

Special values for float and double make it inaccurate to test the equality with ==.
The main Java library uses the standard Object.equals() implementation for all fields,
which for floating point fields means Float.equals() or Double.equals(). They define
equality as bitwise equality, with all NaN representations normalized to the same bit
sequence (and therefore equal to each other). This test checks that the nano
implementation complies with Object.equals(), so NaN == NaN and +0.0 != -0.0.

Change-Id: I97bb4a3687223d8a212c70cd736436b9dd80c1d7

Change-Id: Ibbe944fff83e44a8f2206e18ee9ec6f10661297a

- Get rid of TypeLiteral<T>. It was introduced to read the component
  type of a List<T> at runtime. But we use arrays everywhere else,
  and we can always read the component type of an array type at
  runtime.
- Properly read/write "minor" types (e.g. sint32, sfixed32). The old
  implementation could only read/write data as the "typical" types
  (one per Java type), e.g. java.lang.Integer -> int32, java.lang.Long
  -> int64. So if e.g. an extension specifies sfixed32 as the type, it
  would be read/written in the totally incompatible int32 format.
- Properly serialize repeated packed fields. The old implementation
  doesn't do packed serialization. As an added bonus, and to be more
  aligned with the rest of protobuf nano / main, repeated packable
  extensions can deserialize both packed and non-packed data.
- Split Extension class into a hierarchy so under typical usage a
  large chunk of code dealing with primitive type extensions can be
  removed by ProGuard.

Bug: https://code.google.com/p/android/issues/detail?id=62586
Change-Id: I0d692f35cc2a8ad3a5a1cb3ce001282b2356b041

* commit 'a896c1d8699a3a14aae94b7067339ebc5cccc794':
  Fix MessageNanoPrinter for accessors

* commit 'e7741c064ee4cdc5fa41e6444ed45131672fed97':
  Fix MessageNanoPrinter for accessors

accessors mode switches proto fields away from being public fields (which is
how MessageNanoPrinter found which fields to print via reflection). Add a
pass through the methods looking for generated accessor methods to print
those as well.

Change-Id: I7c47853ecbd5534086f44b25a89dbbe56f63ed03

* commit '6b9d96b2a3b32c141e2b105fcfde4f4b0dfae3f5':
  Avoid class initializers to help ProGuard.

* commit '3f9bd9989c79db575b83e2f96b48c695f30ca153':
  Avoid class initializers to help ProGuard.

Class initializers prevent ProGuard from inlining any methods
because it thinks the class initializer may have side effects.
This is true for static methods, but instance methods can still
be inlined, because to have an instance you will have touched
the class and any class initializers would have run. But
ProGuard only starts inlining instance methods of classes with
class initializers from v4.11b6, and Android uses v4.4 now.

This change tries to avoid the class initializers as much as
possible, by delaying the initialization of the empty array and
some fields' saved defaults until when they're needed. However,
if the message hosts any extensions, they must be public static
final and therefore introducing the class initializer. In that
case we won't bother with lazy initialization.

Change-Id: I00d8296f6eb0023112b93ee135cdb28dbd52b0b8