GitHub PushEvent at 2014-08-22 08:20:00
Repository: android_build
Actor: MrBaNkS
Payload: {"shas":[["6a02cf49807826c047cbe1ffe5cc154c9ab0a3eb","f5e55702d9dd9346a4206725529f35e9a60b39f8@gmail.com","Remove rastakat ascii printing","MrBaNkS",true],["8908ef879dc0cbc7a42061ba70e2413ecf6ceba4","f5e55702d9dd9346a4206725529f35e9a60b39f8@gmail.com","Change ota zip nameing and shell date setup","MrBaNkS",true],["70d7eb02868238aac26ed1295d5638fb734530f5","4ff535844dfc2e03216e86ed8c82949fecbf433e@gmail.com","Backup tool support","AndroidRul3z",true],["4f426e93c9695fcf0c8093b3710e569ebc4bc473","f5e55702d9dd9346a4206725529f35e9a60b39f8@gmail.com","Let vendor handle tones and sounds","MrBaNkS",true],["12860427e47759bc58b5c9f0d2812e7367500a9c","f5e55702d9dd9346a4206725529f35e9a60b39f8@gmail.com","Add support for GNU Make 4.0 and support for OpenJDK*","MrBaNkS",true],["fb0597401265d181c9ec79a5d02d70daed6d9f29","f5e55702d9dd9346a4206725529f35e9a60b39f8@gmail.com","Add support for Inline kernel building (Credits:CM)","MrBaNkS",true],["63b48f08517041f4135595aec8ff182037292bd2","5551c6b7e33c2172ec3f3b3f40b4baf275be9066@gmail.com","envsetup: set OUT_DIR to an absolute path always\n\nOUT_DIR was set to $(TOPDIR)out previously,\nbut $(TOPDIR) was null, so it was a relative path.\nThis broke releasetools, inline kernel building, etc\nsince they require absolute paths.\nFix it so that it is set to $(shell readlink -f .)/out\nif $(TOPDIR) is null.\n\nAlso remove hacks which checked if (OUT_DIR) was out\nand changed it to $(ANDROID_BUILD_TOP)/out to workaround\nthe aforementioned problem.\n\nChange-Id: I459a3b1325a1bbea0565cd73f6acf160d4ed9b39\n\nChange-Id: I52a7a6024f0f2b708c230e53c0152ed138726cc1","Chirayu Desai",true],["7f858c5ca16ae3b8265235ac4627c5b898da8ca5","10f0ac096a170f7d2b072d6443956bdb1ee0d31a@gmail.com","Fixed:Home Button & QS tiles not working without Gapps\n\nConflicts:\n\ttarget/product/large_emu_hw.mk","snak3ater",true],["7812388fb99c027821432fd7c93fbec354ea4304","dc2725693754f1a7a91164b380c7dc13093f6fdb@sonymobile.com","Runtime resource overlay, iteration 2\n\nSupport any number of overlay packages. Support any target package.\n\nUPDATED PACKAGE MATCHING\n------------------------\nIn Runtime resource overlay, iteration 1, only a single overlay package\nwas considered. Package matching was based on file paths:\n/vendor/overlay/system/framework-res.apk corresponded to\n/system/framework-res.apk. Introduce a more flexible matching scheme\nwhere any package is an overlay package if its manifest includes\n\n    <overlay targetPackage=\"com.target.package\"/>\n\nFor security reasons, an overlay package must fulfill certain criteria\nto take effect: see below.\n\nTHE IDMAP TOOL AND IDMAP FILES\n------------------------------\nIdmap files are created by the 'idmap' binary; idmap files must be\npresent when loading packages. For the Android system, Zygote calls\n'idmap' as part of the resource pre-loading. For application packages,\n'idmap' is invoked via 'installd' during package installation (similar\nto 'dexopt').\n\nUPDATED FLOW\n------------\nThe following is an outline of the start-up sequences for the Android\nsystem and Android apps. Steps marked with '+' are introduced by this\ncommit.\n\nZygote initialization\n   Initial AssetManager object created\n+    idmap --scan creates idmaps for overlays targeting 'android', \\\n           stores list of overlays in /data/resource-cache/overlays.list\n   AssetManager caches framework-res.apk\n+  AssetManager caches overlay packages listed in overlays.list\n\nAndroid boot\n   New AssetManager's ResTable acquired\n     AssetManager re-uses cached framework-res.apk\n+    AssetManager re-uses cached 'android' overlays (if any)\n\nApp boot\n   ActivityThread prepares AssetManager to load app.apk\n+  ActivityThread prepares AssetManager to load app overlays (if any)\n   New AssetManager's ResTable acquired as per Android boot\n\nSECURITY\n--------\nOverlay packages are required to be pre-loaded (in /vendor/overlay).\nThese packages are trusted by definition. A future iteration of runtime\nresource overlay may add support for downloaded overlays, which would\nlikely require target and overlay signatures match for the overlay to\nbe trusted.\n\nLOOKUP PRIORITY\n---------------\nDuring resource lookup, packages are sequentially queried to provide a\nbest match, given the constraints of the current configuration. If any\npackage provide a better match than what has been found so far, it\nreplaces the previous match. The target package is always queried last.\n\nWhen loading a package with more than one overlay, the order in which\nthe overlays are added become significant if several packages overlay\nthe same resource.\n\nHad downloaded overlays been supported, the install time could have been\nused to determine the load order. Regardless, for pre-installed\noverlays, the install time is randomly determined by the order in which\nthe Package Manager locates the packages during initial boot. To support\na well-defined order, pre-installed overlay packages are expected to\ndefine an additional 'priority' attribute in their <overlay> tags:\n\n    <overlay targetPackage=\"com.target.package\" priority=\"1234\"/>\n\nPre-installed overlays are loaded in order of their priority attributes,\nsorted in ascending order.\n\nAssigning the same priority to several overlays targeting the same base\npackage leads to undefined behaviour. It is the responsibility of the\nvendor to avoid this.\n\nThe following example shows the ResTable and PackageGroups after loading\nan application and two overlays. The resource lookup framework will\nquery the packages in the order C, B, A.\n\n        +------+------+-     -+------+------+\n        | 0x01 |      |  ...  |      | 0x7f |\n        +------+------+-     -+------+------+\n            |                           |\n        \"android\"                Target package A\n                                        |\n                       Pre-installed overlay B (priority 1)\n                                        |\n                       Pre-installed overlay C (priority 2)\n\nChange-Id: If49c963149369b1957f7d2303b3dd27f669ed24e","Mårten Kongstad",true],["b8a9dc8ff5a10ddd06b306f61b32ea5c9164eb89","e3579b1e47f273529f0f929453e939a68ede9fd1@cyngn.com","New Theme Engine [4/6]\n\nAdds aapt for on device compiling of theme assets\n\nChange-Id: I2f9f4b3e27ddf32b339694f9c6d3b75a12b700d9","Andy Mast",true],["66619e12a3f8e5b815c8e21e0c5a8423d27776dd","bd89d8c9e92648d280255a547e7d70adc7c1f983@gmail.com","ccache: Use system version over prebuilt\n\nIf there is a ccache binary on the\nhost system use it instead of the\nAOSP prebuilt.\n\nChange-Id: I4b1e030713be22167a12bd229a4e35eda7736cd2\nSigned-off-by: Evan Anderson <evan1124@gmail.com>","Evan Anderson",true],["4c8dccb98b170110d54279be325337cd18e6325a","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","build: Cleanup CPU-specific optimizations\n\n * TARGET_ARCH_CPU_VARIANT was a Linaro thing. Now that Android\n   introducted TARGET_CPU_VARIANT, we should use this instead.\n * Added CFLAGS for Krait and Scorpion after the cleanup.\n\nChange-Id: Iafb40ecefa353a1169c22601be4ce80069c3f587","Steve Kondik",true],["fcbb01b561d5d6ea2655527d93a12393c359fd1b","24636a670e51f720a2947fa3e7d8fe65696919ac@gmail.com","add cortex-a5 cpu variant\n\nChange-Id: I369e499d537888eb0f07d900cb50d1424632820e","Konsta",true],["5d23150dc58dc2003e6b525e7df7d26f0a474f33","3be945bfeeebacf832ea217f2164100306661e3a@JustArchi.net","JustArchi's ArchiDroid Optimizations V3\n\n     _             _     _ ____            _     _\n    / \\   _ __ ___| |__ (_)  _ \\ _ __ ___ (_) __| |\n   / _ \\ | '__/ __| '_ \\| | | | | '__/ _ \\| |/ _` |\n  / ___ \\| | | (__| | | | | |_| | | | (_) | | (_| |\n /_/   \\_\\_|  \\___|_| |_|_|____/|_|  \\___/|_|\\__,_|\n\nCopyright (C) 2014 Łukasz \"JustArchi\" Domeradzki\n----------------------------------------------------------------------------------------------------------------\nThis is the squashed commit of countless hours spent on trying to optimize Android to the maximum and push it to the limits.\nPlease give proper credit if you decide to cherry-pick this commit. It includes countless number of full builds and tests, almost 200 hours spent on compiling and testing\n----------------------------------------------------------------------------------------------------------------\nWARNING! These modifcations are pretty DANGEROUS and may cause problems during compiling or running. You may also need to implement some fixes on your own.\n----------------------------------------------------------------------------------------------------------------\nPre-requirements:\n- GCC 4.8, both androideabi and armeabi, these can be added to your local manifest (roomservice.xml). You can use:\n1. Google's GCC toolchain from official google's repo -> https://android.googlesource.com/platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.8 and https://android.googlesource.com/platform/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.8\n2. Linaro 4.8 (proposed) -> https://github.com/JustArchi/Linaro/tree/4.8-eabi and https://github.com/JustArchi/Linaro/tree/4.8-androideabi\n3. SaberMod -> https://github.com/SaberMod\n4. Eventually you can also change TARGET_GCC_VERSION back to 4.7, but 4.8 is highly proposed for performance boost.\n\n- (Optional) Target user, instead of userdebug. You should build with user variant instead of userdebug, as user variant enables odexing and disables additional debug modules, i.e. dalvik debugging. This can be done by multiple ways, i.e. using proper lunch command (i.e. lunching cm_i9300-user instead of cm_i9300-userdebug) or \"brunch device user\", such as \"brunch i9300 user\", if you have this commit -> omnirom@687c588\n----------------------------------------------------------------------------------------------------------------\nImportant notes:\n- ART doesn't work in Android KitKat 4.4.2 with GCC 4.8. This can be fixed with this commit -> JustArchi/android_art@8354d2d\n- If building with custom toolchain like Linaro, it may be possible that kernel won't build right away with \"unknown cpu architecture\" error. It may require some additional fixes, such as this commit -> JustArchi/android_kernel_samsung_smdk4412@6965f2f for smdk4412 kernel. Eventually, just use Google's arm-eabi and Linaro's arm-linux-androideabi, this way you'll build kernel with Google's toolchain and rest of the ROM with Linaro.\n- In some cases stock kernel may not boot when built with GCC 4.8. It looks like this commit -> JustArchi/android_kernel_samsung_smdk4412@803cd15 may help, but don't commit it unless required.\n- Due to O3 optimization, code is significantly larger and may cause problems with oversized images especially for older devices. For example, I couldn't apply O3 because building TWRP recovery failed due to the fact that it didn't fit on recovery's block in my device. In such case you have two options. You may use a hack and manually increase size of the blocks in your BoardCommonConfig.mk, so compiler doesn't yell about that (but you obviously can't flash such images), or you need to go back either to O2 or Os, up to you.\n----------------------------------------------------------------------------------------------------------------\nImportant changes:\n- Added missing Cortex-A9 CPU variant (-mcpu=cortex-a9)\n- Disabled global workarounds for Cortex-A8, they're applied only when you're targetting Cortex-A8 CPU now (-Wl,--fix-cortex-a8)\n- Bumped GCC version to 4.8 from default 4.7, as it performs much better than default 4.7 and gives excellent results\n- Optimized for speed yet more all instructions - ARM and THUMB (-O3)\n- Optimized for speed also parts which are compiled with Clang (-O3)\n- Turned off all debugging code (-DNDEBUG)\n- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)\n- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)\n- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)\n- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)\n- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)\n- Allowed the compiler to assume the strictest aliasing rules applicable to the language being compiled. For C (and C++), this activates optimizations based on the type of expressions. This is only applied to target ARM, nothing has been changed in this matter apart from more precision in warnings (-fstrict-aliasing)\n- Placed each function and data item into its own section, this is required for -Wl,--gc-sections (-ffunction-sections -fdata-sections)\n- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)\n- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)\n- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)\n- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)\n- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)\n- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)\n- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)\n- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)\n- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)\n- Optimized GNU linker, which significantly reduces launching time and memory usage. This is especially visible during booting process, which is a few seconds faster than usual (-Wl,-O1)\n- Applied special --as-needed flag to GNU linker. The flag tells the linker to link in the produced binary only the libraries containing symbols actually used by the binary itself. This not only improves startup times (as the loader does not have to load all the libraries for every step) but might avoid the full initialization of things, which we're not even physically able to use (-Wl,--as-needed)\n- Performed global optimizations that become possible when the linker resolves addressing in the program, such as relaxing address modes and synthesizing new instructions in the output object file (-Wl,--relax)\n- Sorted the common symbols by alignment in descending order. This is to prevent gaps between symbols due to alignment constraints (-Wl,--sort-common)\n- Enabled garbage collection of unused input sections, thanks to -ffunction-sections and -fdata-sections (-Wl,--gc-sections)\n----------------------------------------------------------------------------------------------------------------\n\nFor more information, support, troubleshooting and discussion about my optimizations, please refer to my thread on XDA -> http://forum.xda-developers.com/showthread.php?t=2754997\n\nConflicts:\n\tcore/combo/arch/arm/armv7-a-neon.mk","JustArchi",true],["4eacb9bfeb03f73d5b7f2c1efb125f2e69a31bd1","2b64bd5dfb5d90438e13f0ceac378ad1d28c1078@google.com","Specify -mcpu=cortex-a15 for krait CPU variants.\n\nBug: 11178216\n\nChange-Id: I9922e4cd5ba27e3857798aae5c84299e26e054ea","Ian Rogers",true],["4378e0fe2200490f7b28b928e4ea8faec44f3df4","feade4f1629fc8e86b665512da2848436719d0b1@gmail.com","build: no longer build emulator by default\n\nThis is just increasing build times when most people are not using it.\nLet's speed up builds a bit.\n\nBuilding emulator should still be possible by appending BUILD_EMULATOR=true\nto the build command\n\nPS2: Let's keep the darwin warning.\n\nChange-Id: Ibd8e2b90455bd603a691c7b95466068b6fae212a\nSigned-off-by: Andrew Warfield <hiasant@gmail.com>","Andrew Warfield",true],["febd21913ff7db216f9d082f907adc3bd5ddb34c","1a8755ca18bea68fa43e2fa2d5d89fde446d3151@cyngn.com","build: Set ccache base to build top\n\nThis enables ccache sharing between different build tree paths.\n\nChange-Id: I99636bdd2779a6ccf0649f027e35cf67df44b6ae","Tom Marshall",true],["205d5375997ff6b019d63af99c6e2a3aa0f5d207","d1b2965cdece294059ce3a4cfe29cbdc2025351c@gmail.com","build: use /usr/bin/env to call python\n\nHardcoding the path to python instead of env is not recommended.  This\ncan break the build in some Linux environments that link /usr/bin/python\nto python3.\n\nChange-Id: I4c62eb391acc6d468ce24ac8640834e965e76e78","Andrew Bartholomew",true],["2c615d9a5c7141f3514d8bc3f7b5fbd9f2dd438c","f5e55702d9dd9346a4206725529f35e9a60b39f8@gmail.com","Merge tag 'android-4.4.4_r2.0.1' of https://android.googlesource.com/platform/build into kk\n\nAndroid 4.4.4 Release 2.0.1","MrBaNkS",true]],"size":19,"ref":"refs/heads/kk","head":"2c615d9a5c7141f3514d8bc3f7b5fbd9f2dd438c"}