99ae76e24a
Generate and store minimum amount of information necessary to create backtraces in native tools (for crashes and profilers). The data is compressed and takes <5% relative to JIT code size (which is less than recent stack map savings; so win overall). Averages for non-compiled run of maps which filled JIT code cache to ~4MB: Q: code:1.55kb/method data:0.738kb/method debug:0.064kb/method(*this CL*) P: code:1.62kb/method data:0.956kb/method debug:0.835kb/method(if enabled) I also measured the P to Q on-disk stack maps savings in CL/762841 as ~28% (not all of that is applicable to JITed code, so that is an overestimate). Bug: 111350693 Test: Device boots, mini-debug-info is generated. Change-Id: I95883bd4f2d5c2308149ab0ba641b0a703c7f81b |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
Android.mk | ||
Changes.md | ||
CleanSpec.mk | ||
OWNERS | ||
README.md | ||
Usage.txt | ||
buildspec.mk.default | ||
envsetup.sh | ||
help.sh | ||
navbar.md | ||
tapasHelp.sh |
README.md
Android Make Build System
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.