diff options
author | Johann <johannkoenig@google.com> | 2016-08-26 18:13:07 -0700 |
---|---|---|
committer | Johann <johannkoenig@google.com> | 2016-09-19 12:16:03 -0700 |
commit | fad70a358b9ab832f5f2ece1609936b80b649c71 (patch) | |
tree | b20f9138d6269acfbaf691834a8ac1a9de96c2ac | |
parent | aa0eb67bf7c009b515ec5130cca71bf8f4a5340b (diff) | |
download | libvpx-fad70a358b9ab832f5f2ece1609936b80b649c71.tar libvpx-fad70a358b9ab832f5f2ece1609936b80b649c71.tar.gz libvpx-fad70a358b9ab832f5f2ece1609936b80b649c71.tar.bz2 libvpx-fad70a358b9ab832f5f2ece1609936b80b649c71.zip |
Remove -fno-strict-aliasing flag
The referenced bug was fixed by saving neon registers. That this had any
effect was coincidental.
Both chromium and Android build with clang and neither uses this flag.
Change-Id: I470247d6fd9226fc207b42a187105581a94badc3
-rwxr-xr-x | configure | 8 |
1 files changed, 0 insertions, 8 deletions
@@ -578,14 +578,6 @@ process_toolchain() { # check_add_cflags also adds to cxxflags. gtest does not do well with # -Wundef so add it explicitly to CFLAGS only. check_cflags -Wundef && add_cflags_only -Wundef - case ${CC} in - *clang*) - # libvpx and/or clang have issues with aliasing: - # https://code.google.com/p/webm/issues/detail?id=603 - # work around them until they are fixed - check_add_cflags -fno-strict-aliasing - ;; - esac if enabled mips || [ -z "${INLINE}" ]; then enabled extra_warnings || check_add_cflags -Wno-unused-function fi |