art/dex2oat, branch cm-13.0

Build dex2oat without asan instrumentation.

2016-03-16T22:58:48+00:00

Instead of a two pass build to use ASAN,
build dex2oat with LOCAL_SANITIZE:=never.

BUG: 22233158

Change-Id: Ic881dc10c386c7fa81329d465182a23eb2387e41

art: fix dex2oat watchdog timeout

2016-02-23T21:17:31+00:00

Merging of Android 6.0.1 release 3 (Change-Id:
I23fd56f2c1a3e8e8b993a151a794e18f3569912e) reverted the watchdog
timeout back to old short one.

PackageManagerService in frameworks/base/ is still using 60 minutes as
watchdog timeout (Change-Id: Ia8f089ea340f21023abb8a58ddb3aede8b2b728c)
and I think this should match that or revert PackageManagerService side
back to also using 10-minute timeout as documented here on dex2oat.

I modified the old long timeout to match the change from 6.0.1_r3 merge
(Change-Id: I425b19ab305cfaa43f6bddc3a892be892acaf513) which introduced
slightly shorter (30 seconds) timeout here to make sure that "dex2oat
kills itself before the system server watchdog kills the system because
of the long installation".

Change-Id: I79e4bed34df7d964b9c4cac0d1c344cf773961b7

Merge tag 'android-6.0.1_r3' of https://android.googlesource.com/platform/art into HEAD

2015-12-08T11:20:54+00:00

Android 6.0.1 release 3

Change-Id: I23fd56f2c1a3e8e8b993a151a794e18f3569912e

dex2oat: Increase timeout to allow slow CPUs to finish compilation

2015-11-07T09:24:29+00:00

Change-Id: Ib9f19e0acf1a0a5b90d8b7ef2a0daf224cb2aec1

ART: Decrease dex2oat watchdog timeout

2015-10-09T03:46:33+00:00

Keep the dex2oat watchdog timeout lower than the package manager
timeout, so that dex2oat kills itself before the system server
watchdog kills the system because of the long installation.

Bug: 23629410

(cherry picked from commit 540138ae55ac1909606a436d7f52e20146c56657)

Change-Id: I425b19ab305cfaa43f6bddc3a892be892acaf513

ART: Tuning compiler thread count for application runtime

2015-10-06T09:20:37+00:00

dex2oat decides the number of compiler threads to be spawned based
on the number of cores in the system. Using this max possible compiler
threads causes over parallelization on some platforms and there by
leads to longer install times. Reducing to fewer threads on these
platforms, improves this time by 60% to 100%.
Some APPs will call dex2oat at the first launch time(runtime). The
thread count tuning is needed for such scenario.

Change-Id: Id3a545f0300f93397627beeb697a7b7cfd912d52

ART: Clean up less in dex2oat

2015-09-28T22:18:20+00:00

In non-debug builds, clean up even less. We already did not shut
down the runtime. Also skipping the compiler driver and the
verification results removes all major points of destructor
performance.

Tested with a common large app on Nexus 9. Time between dex2oat timing
message and executable exit (log from immediately-after log echo)
[w/o swap, w/ swap].
Before:  2.409s / 48.774s
After:   0.132s /  0.188s

Bug: 24199200
Change-Id: I5d8c17f8e28796545cfbb3887c07c92905f9b48d
(cherry picked from commit 3f30e1219dd76f78bb9b6504e696a04a3dfae564)

Tighten default inlining settings when using the space filter.

2015-08-07T11:22:28+00:00

(cherry picked from commit a215b95d03cfe713018a245553b74d7eeee813df
and amended)

Bug: 21868508
Change-Id: Ic83813a966cef18e59447083926bf033aa587154

Allow for fine tuning the inliner.

2015-07-30T09:40:39+00:00

Bug: 21868508

(cherry picked and squashed from commits
ec74835a7e4f2660250a2f3f9508cbbe5269e49a and
0941b9d48a9a8c6d80a1af7a0d0fc9f80fe2b9a1)

Change-Id: I1750e6bea20321d04680132281a6c2924531c5ae

Add implicit null pointer and stack overflow checks for Mips.

2015-07-03T16:29:27+00:00

(cherry picked from commit 22bb5a2ebc1e2724179faf4660b2735dcb185f21)

Bug: 21555893
Change-Id: I2a995be128a5603d08753c14956dd8c8240ac63c