| commit | 55220942ed46c2f5c0f4e64af8c5958342dd5aa3 | [log] [tgz] |
|---|---|---|
| author | Ivan Lozano <ivanlozano@google.com> | Wed Feb 06 11:09:05 2019 -0800 |
| committer | Ivan Lozano <ivanlozano@google.com> | Wed Feb 06 11:09:05 2019 -0800 |
| tree | 0adc1eeb65a5cfe99bcef04c5263db4495495ce2 | |
| parent | 7bd8753381d8fa6a1daec9a831b07fdd8f293446 [diff] |
Don't enable CFI diagnostics in include paths. Don't enable CFI diagnostics by default when applying it in include paths. Part of a broader effort to remove diagnostics mode from CFI across the board. This should reduce performance overhead and also allows the minimal runtime to work when other ubsan sanitizers are enabled. CFI stack dumps should include a CFI related function, so it should be apparent when a crash is CFI-related. Bug: 117417735 Test: make -j Change-Id: I3d6326e06d7aa7d9c00382f336301ecb822ae7ec
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.