diff options
author | Brian Duff <bduff@google.com> | 2015-02-21 15:22:43 -0800 |
---|---|---|
committer | Brian Duff <bduff@google.com> | 2015-04-28 13:01:48 -0700 |
commit | dac7e02d2b9942953481bbe88241d4bf914ef30c (patch) | |
tree | c7b2f9f28190837dbf688b5c6d6df607fa2469f4 /javanano/src/main | |
parent | ec19be2f3c7a95f3b7d6d0ff7055daead9284d8d (diff) | |
download | protobuf-dac7e02d2b9942953481bbe88241d4bf914ef30c.tar.gz protobuf-dac7e02d2b9942953481bbe88241d4bf914ef30c.tar.bz2 protobuf-dac7e02d2b9942953481bbe88241d4bf914ef30c.zip |
Expose generate_clear as an option.
I wasn't able to get the clear() method to inline into the
constructor when optimizations are on in proguard. As a result,
every message has an extra superfluous kept method assuming the
app never uses clear() directly.
There are a couple of instances where setting this option false is
necessary in order to get code dexing successfully without hitting
the method limit, e.g. https://goto.google.com/tltzq
In this example, I tried turning on the method/inlining/unique and
method/inlining/short optimizations before resorting to adding the
generate_clear option, but the method count did not decrease. The
clear() methods were contributing over a thousand extra methods.
Change-Id: If6a9651d6a59cdf70b1040d8248779710ac73105
Diffstat (limited to 'javanano/src/main')
0 files changed, 0 insertions, 0 deletions