The optimization step of ProGuard can be switched off with the
-dontoptimize option. For
more fine-grained control over individual optimizations, experts can use the
with a filter based on the optimization names listed below. The filter works
like any filter in ProGuard.
The following wildcards are supported:
matches any single character in an optimization name.
matches any part of an optimization name.
An optimization that is preceded by an exclamation mark '!' is
excluded from further attempts to match with subsequent
optimization names in the filter. Make sure to specify filters correctly,
since they are not checked for potential typos.
only performs the two specified peephole optimizations.
For example, "!method/propagation/*" performs all optimizations,
except the ones that propagate values between methods.
performs all peephole optimizations.
Some optimizations necessarily imply other optimizations. These are then
indicated. Note that the list is likely to change over time, as optimizations
are added and reorganized.
Marks classes as final, whenever possible.
Merges classes vertically in the class hierarchy, whenever possible.
Merges classes horizontally in the class hierarchy, whenever possible.
Removes write-only fields.
Marks fields as private, whenever possible.
Propagates the values of fields across methods.
Marks methods as private, whenever possible (devirtualization).
Marks methods as static, whenever possible (devirtualization).
Marks methods as final, whenever possible.
Removes unused method parameters.
Propagates the values of method parameters from method invocations to
the invoked methods.
Propagates the values of method return values from methods to their