| commit | 88ac49ee94f05ddbff5e3eae6ce07957ec95e5f2 | [log] [tgz] |
|---|---|---|
| author | Mathias Rav <mathiasr@google.com> | Fri Mar 09 13:11:02 2018 +0100 |
| committer | Mathias Rav <mathiasr@google.com> | Fri Mar 09 13:11:02 2018 +0100 |
| tree | ea1b663f95dd7bcc67d139b9097a109484bb8259 | |
| parent | 33ba362dcf942157bac2fbc5a61272904890a2bd [diff] |
Run CF backend on Art tests
This reverts commit c872f06b (2018-03-07) which reverted commit 66f599c1
("Run CF backend on Art tests", 2018-03-07).
Add CompilerUnderTest.D8_AFTER_R8CF for testing the combination of R8/CF
and D8. For tests that have both DEX and Classfile inputs, R8/CF
processes only the Classfile inputs, and D8 processes the DEX inputs
and the Classfile output of R8.
Add D8_AFTER_R8CF to TestCondition.R8_COMPILER and D8_COMPILER, since
these TestCondition cover cases where respectively R8 and D8 run.
Add TestCondition.R8DEX_COMPILER which covers only the cases when R8 is
run with the DEX backend.
Add TestCondition.D8_NOT_AFTER_R8CF_COMPILER which covers the cases when
D8 is run directly on Classfile inputs without involving R8/CF.
Add TestCondition.D8_AFTER_R8CF_COMPILER for tests involving R8/CF.
Change most instances of R8_COMPILER to R8DEX_COMPILER in lists of
expected exceptions, and add a few new expected exceptions for R8/CF.
Make create_art_tests.py generate Art test cases in
com.android.tools.r8.art.none.r8cf, but don't create any test cases
with DexTool.DX or JACK.
Change-Id: I82ea712184d8845d32c2603252e4262e6eb23ad4The 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.