Proguard optimizations |
||
Issue descriptionGeneric bug for proguard flags that are found which are beneficial to be turned on/off.
,
Jun 23 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/2d8e46f62869097c447480592851464f09ebf965 commit 2d8e46f62869097c447480592851464f09ebf965 Author: Sam Maier <smaier@google.com> Date: Thu Jun 23 13:59:32 2016
,
Jun 27 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/4c9e68f1babf54ab204de62cda5b2625bd80bd77 commit 4c9e68f1babf54ab204de62cda5b2625bd80bd77 Author: Sam Maier <smaier@google.com> Date: Fri Jun 24 15:19:49 2016
,
Jul 28 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fc1a80d5d329dd4a1cce9886cadf85100f1edcb4 commit fc1a80d5d329dd4a1cce9886cadf85100f1edcb4 Author: smaier <smaier@chromium.org> Date: Thu Jul 28 20:28:08 2016 Running 3 ProgGuard optimization passes. This increases release build time by 30s, reduces our .dex size by 33k, and saves us 2k memory per process. BUG= 620371 Review-Url: https://codereview.chromium.org/2166813002 Cr-Commit-Position: refs/heads/master@{#408464} [modify] https://crrev.com/fc1a80d5d329dd4a1cce9886cadf85100f1edcb4/base/android/base_proguard_config.flags
,
Aug 18 2016
Our ProGuard configs are pretty well optimized (save obfuscation), I don't forsee any work on optimizing them further. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jun 20 2016