| commit | b936b9521d6d003d0d58b6a9a9ce3c771d5a59a8 | [log] [tgz] |
|---|---|---|
| author | Jinseong Jeon <jsjeon@google.com> | Tue Feb 13 14:28:10 2018 -0800 |
| committer | Jinseong Jeon <jsjeon@google.com> | Tue Feb 13 14:28:10 2018 -0800 |
| tree | 3991f31f1466b7a8acc4b27fe85bb6e486449c2c | |
| parent | 38f0d86ca9325bd64daf23550898272eb4e1b053 [diff] |
Add the chosen field renaming back to NamingState. NamingState#assignNewNameFor() litereally assigns a new name for given proto. It is up to Minifier which new name to use, though. For example, MethodMinifier computes the frontier map of interface hierarchy and tries to assign and reuse a unique name that avoids conflicts among interfaces. To do so, for each state that corresponds to different interface, it keeps trying to assign a new name until the new name is available at all interfaces. At the end, only the chosen, unique name is stored at the top-level state to reuse (for the same name) or avoid conflicts. FieldMinifier misbehaves for -useuniqueclassmembernames: it should assign the same rename to the same name if any. The bug was, it never stored which name was chosen in the NamingState. (Thus, always returns new names.) Bug: 72858955, 73149686 Change-Id: Ia293d47e9e2e4dcc07fc46a1f59cc02637b9a5b3
The R8 repo contains two tools:
D8 is a replacement for the DX dexer and R8 is a replacement for the Proguard shrinking and minification tool.
The R8 project uses depot_tools from the chromium project to manage dependencies. Install depot_tools and add it to your path before proceeding.
The R8 project uses Java 8 language features and requires a Java 8 compiler and runtime system.
Typical steps to download and build:
$ git clone https://r8.googlesource.com/r8 $ cd r8 $ tools/gradle.py d8 r8
The tools/gradle.py script will bootstrap using depot_tools to download a version of gradle to use for building on the first run. This will produce two jar files: build/libs/d8.jar and build/libs/r8.jar.
The D8 dexer has a simple command-line interface with only a few options.
The most important option is whether to build in debug or release mode. Debug is the default mode and includes debugging information in the resulting dex files. Debugging information contains information about local variables used when debugging dex code. This information is not useful when shipping final Android apps to users and therefore, final builds should use the --release flag to remove this debugging information to produce smaller dex files.
Typical invocations of D8 to produce dex file(s) in the out directoy:
Debug mode build:
$ java -jar build/libs/d8.jar --output out input.jar
Release mode build:
$ java -jar build/libs/d8.jar --release --output out input.jar
The full set of D8 options can be obtained by running the command line tool with the --help option.
R8 is a Proguard replacement for whole-program optimization, shrinking and minification. R8 uses the Proguard keep rule format for specifying the entry points for an application.
Typical invocations of R8 to produce optimized dex file(s) in the out directory:
$ java -jar build/libs/r8.jar --release --output out --pg-conf proguard.cfg input.jar
The full set of R8 options can be obtained by running the command line tool with the --help option.
Typical steps to run tests:
$ tools/test.py --no_internal
The tools/test.py script will use depot_tools to download a lot of tests and test dependencies on the first run. This includes prebuilt version of the art runtime on which to validate the produced dex code.
In order to contribute to D8/R8 you have to sign the Contributor License Agreement. If your contribution is owned by your employer you need the Corporate Contributor License Agreement.
Once the license agreement is in place, you can upload your patches using ‘git cl’ which is available in depot_tools. Once you have a change that you are happy with you should make sure that it passes all tests and then upload the change to our code review tool using:
$ git cl upload
On your first upload you will be asked to acquire credentials. Follow the instructions given by git cl upload.
On successful uploads a link to the code review is printed in the output of the upload command. In the code review tool you can assign reviewers and mark the change ready for review. At that point the code review tool will send emails to reviewers.
For questions, reach out to us at r8-dev@googlegroups.com.
For D8, find known issues in the D8 issue tracker or file a new D8 bug report.
For R8, find known issues in the R8 issue tracker or file a new R8 bug report.