* 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

* 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

* commit '6a6b3b384c6084b3ce0de360b6dcb74a82bc23bb':
  Nano: don't generate accessor methods for nested methods

* commit 'cea499acf68b35921b956785c26c0e6f18c241c1':
  Nano: don't generate accessor methods for nested methods

For nested message objects, don't generate accessor methods because they have
a default value that is not a valid value (null), so there is no reason to have
get/set/has/clear methods for them. Clients and protos (while serializing) can
check against the invalid value to see if it's been set.

Change-Id: Ic63400889581271b8cbcd9c45c84519d4921fd4b

* commit '98c9208a616a97adf00bf1b3265e0f589c191d95':

* commit 'b6089cca5248f19832dde54faaad62891ff8bd25':

* commit '485b7645fea855d55b281185c7299ee9d7ab7f9a':

* commit 'c4c4a562672068fb89ea4e65408dd53de2ed8f1f':

* commit '0143d32d6ff0aad17873b486966c7a58efa04811':
  Align with main: two ways of parsing repeated packable fields.

* commit 'f5271c9ca4a237221c0ba722dc548050ad131064':
  Align with main: two ways of parsing repeated packable fields.

It is a requirement for parsing code to handle packed and unpacked
forms on the wire for repeated packable fields. This change aligns
the javanano's behavior with the java's.

Bonus: optimize array length calculation when parsing repeated
fixed-size-element-type fields.

Bonus 2: lose "xMemoizedSerializedSize" for repeated enum fields,
and make the serialized size calculation match that for repeated
int32 fields.

Change-Id: I8a06103d9290234adb46b0971b5ed155544fe86a

* commit '0afd5a4d782037ea641d75d595cf5d38ed6978ac':
  Update MessageNano#toString() to return mostly valid TextFormat.