| commit | 898a518f7e87d5c65bd91deb0962b1592a68d30f | [log] [tgz] |
|---|---|---|
| author | Jinseong Jeon <jsjeon@google.com> | Tue Jun 26 16:39:37 2018 -0700 |
| committer | Jinseong Jeon <jsjeon@google.com> | Tue Jun 26 23:42:24 2018 +0000 |
| tree | 232e89078f2244a016e9db145a3db4595c47c351 | |
| parent | 8fab3f59182d503511d7a37167bbab6c17cf74c9 [diff] |
Apply the prior lense _after_ finding members to be bound. Neither map applier nor member rebinding analysis honors the given prior lense properly: see http://b/110067602#comment2 for more details. Even class merger is now playing its role, and here are several constraints that those should have met (i.e., we were lucky so far(TM)). * -applymapping focused on the use case of testing apps: the app under test is already minified, where the testing app should be consistently remapped and renamed. In this case, the original app is given as a lib, not program classes. Such types in the lib that need to be fixed are rather encoded as lense. So, it makes sense to put map applier upfront. * member rebinding analysis only cares about class hierarchy: looking up class definitions and traversing upwards to find the right super type. Also, the end result is mappings inside the class hierarchy, whereas the lense result of map applier is from one world to another, i.e, their results are somewhat orthogonal. That raised the question: *when* to apply the previous lense for member rebinding analysis. Member rebinding analysis should do its job on the original world, and see if that rebound member could be remapped to the other world (via the previous lense). * Any analysis that directly fixes types in class definitions by itself should wrap the application as a direct-mapped one. Otherwise, any other following analysis (e.g., member rebinding after map applier) that tries to traverse class hierarchy will see inconsistent type-to-class maps, and may not be able to look up class definitions. Expected behaviors are tested by existing tests, including: ...memberrebinding.CompositionalLenseTest ...naming.ApplyMappingTest ...classmerging.ClassMergingTest Bug: 110067602 Change-Id: Ieddfde51133482c1ac8530568b426935400aa2f0
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.