5297f237f2d5e40967dcfe19bfd11639b0e7223f |
|
05-Dec-2014 |
Andrew Hsieh <andrewhsieh@google.com> |
misc fixes in r10d 1. Remove hack for server where android-13,15,17 were missing 2. Remove --disable-libquadmath 3. Fixed build-gnu-libstdc++.sh thumb build where "-ffunction-sections -fdata-sections" were dropped 4. Fixed llvm clang3.5/windows build where mingw-64 complains about -fPIC 5. Fixed bashism in make-standalone-toolchain.sh 6. Fixed "package-release.sh --separate-64" 7. Relaxed patch-sources.sh against non-existance patch directory 8. Refresh build/tools/toolchain-patches/gcc/0010-Fix-PR-target-63209.patch 9. Fixed warning about unused vars in cpu-features.c 10. Fixed sources/android/support/Android.mk about -fvisibility-inlines-hidden is only foo C++ 11. Fixed tests/build/check-armeabi-v7a-prebuilts/build.sh on MacOSX 10.6.8 12. Fixed tests/build/issue64679-prctl/build.sh to include GLES2/gl2ext.h which can be compiled alone now 13. Excluded tests/device/b8708181-Vector4/jni/Vector4.cpp from clang3.4 14. Removed some comments in tests/device/test-libc++-*-full/jni/Android.mk 15. misc run-test.sh fixes 16. Disable integrated-as for clang in tests/build/issue79115-confusing-ld.gold-warning Change-Id: I0afb2c00642dd61d81fd4842532d1b3c4029655b
|
fea3cfa31dbd1e08ee0d9e4889ccd233a865dd9c |
|
17-Nov-2014 |
David 'Digit' Turner <digit@google.com> |
tests/build/check-armeabi-v7a-prebuilt: run on Darwin. Get the 'readelf' binary from toolchains/ to allow this test to run properly on Darwin. Change-Id: I45af6ddc744e2686cd8d4187b8beef586c3a3355
|
1289c4187335656b160e3b182757949537d90772 |
|
13-Feb-2014 |
Andrew Hsieh <andrewhsieh@google.com> |
Enable more armeabi-v7a-hard tests 1. Set _NDK_TESTING_ALL_=yes to 1) expand "APP_ABI=all" into "APP_ABI=armeabi armeabi-v7a x86 mips armeabi-v7a-hard", and 2) install armeabi-v7a-hard into its own libs/armeabi-v7a-hard directory and tested separately 2. Most tests are compiled with "APP_ABI=all" already. Add armeabi-v7a-hard for those tests with APP_ABI=armeabi-v7a, except for some tests in test-cpufeatures which filter out -march=armv7-a from (per-abi global) TARGET_CFLAGS which break test_android_setCpuArm_1 because "-mhard-float -mthumb" can't go together w/o -march=armv7-a Change-Id: I5e571eff233c78b3e86e563d868e599d505e28ba
|
0136e5405c99a3fbe1be109ee8ff186475c0d99a |
|
03-Jul-2012 |
Andrew Hsieh <andrewhsieh@google.com> |
Change default GCC to 4.6; Build separate gnu-libstdc++ for GCC 4.4.3 and GCC 4.6 All target prebuilt will be built with GCC 4.6. GNU libstdc++ is GCC dependent. GCC 4.6 seems to take header/libraries built by GCC 4.4.3, but the reverse isnĘžt true. With this CL GCC will now use its own version of libstdc++. make-standalone-toolchain by default install GCC 4.6. Use --toolchain to select GCC 4.4.3. Change-Id: I2f4042501989fbfce94a521e6c24e1102d95a3aa
|
be151788b1ef78ac67a00510aafcdeda83a5b446 |
|
08-Mar-2012 |
David 'Digit' Turner <digit@google.com> |
check-armeabi-v7a-prebuilts: loosen checks due to binutils-2.19 bugs It looks like the check-armeabi-v7a-prebuilts script cannot work properly when looking at machine code generated with GCC 4.4.3 + binutils 2.19 Document the madness in the script, and make it pass with the binaries that we're going to provide in the next release (even though they contain invalid ELF aeabi tags). I have checked manually, by looking at the disassembled output that they're good. Once we switch to binutils 2.21 or better, we'll be able to make the script work as expected and not worry about this problem anymore. The reason why this wasn't detected earlier is because I was using a GCC 4.4.3 + binutils 2.21 toolchain to generate my prebuilts. I had to run the NDK rebuild + packaging scripts from scratch, and run the test suite on the results to see the problem. Change-Id: I1ac331fe2a9a6fb1a9c32b52b6c5b42afd18296b
|
96de6d98a79d3cd031b09f35e6659b1dd5645278 |
|
07-Mar-2012 |
David 'Digit' Turner <digit@google.com> |
Fix armeabi-v7a prebuilt binaries (GNU libstdc++ + STLport) Due to a typo in build-gnu-libstdc++.sh and build-funcs.sh, the armeabi-v7a prebuilt binaries were built assuming a VFPv3-D32 capable CPU (i.e. 32 FPU double registers, while the ABI only mandates VFPv3-D16). This resulted in crashes when running programs linked to it on Tegra devices and other non-NEON capable ones. Fixes http://code.google.com/p/android/issues/detail?id=26199 + new unit test that checks that all our armeabi-v7a prebuilt binaries are of the correct type. Change-Id: I567e202921881f76d1e70bed930182ea7d517b4e
|