Bug workaround specifically for gcc 4.7.0
llvm: Use -fno-strict-aliasing

llvm takes too many shortcuts to make fixing it (and keeping it fixed w/
future versions) a small project.

Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
Fix for GCC 4.7.x

GCC version 4.7.1 has the same bug as GCC 4.7.0.
This make expands the earlier fix to cover all 4.7.x versions

Change-Id: I5ab1720f627702eba11f7686a668f9ddbaa21267
Merge branch 'jb-release' of https://android.googlesource.com/platform/external/llvm into aosp
Merge branch 'jb-mr1-release' of https://android.googlesource.com/platform/external/llvm into mr1-staging

Change-Id: Ibdc6764c12804710b11fef3a6ce8b5be0fe7346c
llvm: Fix building libLLVMSupport.

Change-Id: I8719e13d09031d5f99341feb352fa446562c1033
Merge tag 'android-4.3_r2.1' into cm-10.2

Android 4.3 release 2.1
Merge tag 'android-4.3_r3.1' of https://android.googlesource.com/platform/external/llvm into cm-10.2

Android 4.3 Release 3.1
Merge tag 'android-4.4_r1' into cm-11.0

Android 4.4 Release 1.0
Merge remote-tracking branch 'cm/cm-11.0' into HEAD