From: Johann <johannkoenig@google.com>
Date: Sat, 27 Aug 2016 01:13:07 +0000 (-0700)
Subject: Remove -fno-strict-aliasing flag
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9ed9cedae10545b8a31bf4777aa1401eeb7a2444;p=libvpx

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
(cherry picked from commit fad70a358b9ab832f5f2ece1609936b80b649c71)
---

diff --git a/configure b/configure
index c96691ba3..1bc0863e6 100755
--- a/configure
+++ b/configure
@@ -606,12 +606,7 @@ process_toolchain() {
         check_add_cflags -Wuninitialized
         check_add_cflags -Wunused-variable
         case ${CC} in
-          *clang*)
-              # libaom 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
-          ;;
+          *clang*) ;;
           *) check_add_cflags -Wunused-but-set-variable ;;
         esac
         if enabled mips || [ -z "${INLINE}" ]; then