commit | f5c5f55563f307888b6acec54c1026de64f7e63d | [log] [tgz] |
---|---|---|
author | Morten Krogh-Jespersen <mkroghj@google.com> | Fri Nov 04 09:28:11 2022 +0100 |
committer | Morten Krogh-Jespersen <mkroghj@google.com> | Fri Nov 04 09:28:11 2022 +0100 |
tree | 60fef222e91b94699af6dc705aaa1af39176037f | |
parent | eb604a396dbdfec8977bc5c7ff6457fc906455a2 [diff] |
Revert "Add disabled logic for using new-filled-array for more things." This reverts commit 245e2195d38b306d2312723d284850bdd651b316. Revert "filled-new-array: Add support for InvokeNewArray to Enum Unboxing" This reverts commit 268310a01add17ce7c228e4ff346f35b2951ac14. Revert "filled-new-array: Add support for InvokeNewArray to proto shrinker" This reverts commit 35519c21df96abe4c08f386d56851c7cd66ad946. Revert "filled-new-array: Add support for InvokeNewArray to Enqueuer" This reverts commit cc0b4f77c1d9ae166b1eee08ba45e637aafb7291. Revert "filled-new-array: Add support for InvokeNewArray to IdentifierNameString" This reverts commit 1e7c97a740695a2545fc3e62485cd5f7f705df96. Revert "filled-new-array: Update ArrayWithDataLengthRewriteTest and IdentifierNameStringMarkerTest" This reverts commit c39e92437ef27e368f80813d002b9bd99e783a13. Revert "Enable and remove InternalOptions' experimentalNewFilledArraySupport" This reverts commit 75ee6b775dae6979c5808f810fcc02ecb8c97fd5. Bug: b/246971330 Change-Id: I9052346aa01382bd2133dd4f5aded049a2cccc84
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 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 a jar file: build/libs/r8.jar
which contains both R8 and D8.
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 -cp build/libs/r8.jar com.android.tools.r8.D8 --output out input.jar
Release mode build:
$ java -cp build/libs/r8.jar com.android.tools.r8.D8 --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, please send an email to r8-dev@googlegroups.com to be added as a contributor.
After being added as a contributer 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.