Keep sanitizers in diagnostics mode but don't recover from them so we
get errors in tombstones.
Bug: 110791537
Test: mma -j
Change-Id: Ib5e7d110ded68e19e276d79f99f648fea3f70078
Previously there was no other sanitization, so in order for the
blacklist to be picked up CFI had to be enabled. With integer_overflow
enabled, we no longer need it enabled explicitly in the build file.
Since libavc is a static library, both CFI and non-CFI variants will
be built and linked accordingly.
If libavc is used as a shared library in the future, we'll need to
explicitly re-enable CFI in the build file.
Bug: 63926619
Test: Library builds.
Change-Id: I2646e1422c29073d2e622ded1a9074426b186130
CFI does not recognize assembly functions as valid indirect call
targets.
Test: no cfi checks in libavcdec/libavcenc
Change-Id: I173eeaad0a908bfd055d21a5c7eec9634ba0ac95
Since ARM neon instructions were only used on armv7-a-neon
architecture variant, the default implementation for this
library doesn't use these advanced SIMD instructions.
Bug: 65568114
Test: lunch aosp_arm64; emulator # on oc-mr1-dev; boot to home screen
Change-Id: I7d0c75045fc69523861ed5a00f6033ac327f4031
Software codecs and their dependencies are marked as VNDK (or just
vendor_available:true for static/header libs).
Bug: 37343418
Test: build the software codecs with BOARD_VNDK_VERSION=current
Change-Id: I84a07188fda0e89e422caee634cb12ec82568028
