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
llvm: Add workaround for STLport not being a full C++11 STL

llvm checks for C++11 support in the compiler, and assumes the
STL has full C++11 support if the compiler does.
However, for the combination of gcc 4.7 and STLport, that assumption
is incorrect -- the compiler supports rvalue references just fine, but
the STL hasn't caught up yet.

Longer term, the better fix would be to fix STLport.

Change-Id: I20237a19a3835faee583f429749751ee3c4843f6
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
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 branch 'linaro_android_4.2.1' of http://android.git.linaro.org/git-ro/platform/external/llvm into jb-mv-wip
Merge branch 'jb-mv' of git://github.com/Mustaavalkosta/android_external_llvm into classified