GitLab

After apply this patch:
1. Use build-abcc.sh with --only-assets to generate toolchain assets.
3. mmm ndk/tests/abcc
4. make systemimage

Also 2 modifications.
1. Change name abcc-$abi.apk to abcc-$abi-unsigned.apk for clearity.
2. Add prebuilts dir into .gitignore.

Change-Id: Iadace270113209e958439250e6db75c9ed6ea0b8

Change-Id: I0a7c73a1021dd501abf5ec50a53f0d00778565d3

1. build-device-llvm.sh use --abis instead of --arch
2. build-device-llvm.sh keeps BUILD_OUT explicitly specified
3. wrap more commands with "run" (better in --verbose)
4. more arch-specific flags

Change-Id: Ia453945215ada4532a24ab11f54ff195898c49ec

Change-Id: I7791e7919b1feb93e59e9e3932597ec0673a723f

This CL depends on:

https://android-review.googlesource.com/#/c/63863/
https://android-review.googlesource.com/#/c/63862/

Change-Id: I70d48fd01175a890d410a9feda932912572d3a0d

Use prebuilts/assets or $NDK_TARGET_SYSROOT built this way:

 # prebuilts/assets
  export NDK=your-AOSP-path/ndk
  cd $NDK ; ./build/tools/dev-cleanup.sh
  ./build/tools/download-toolchain-sources.sh /tmp/ndk-$USER/src
  ./build/tools/build-on-device-toolchain.sh --no-sync --abi=armeabi-v7a \
    --out-dir=$NDK/tests/abcc/prebuilts/assets/armeabi-v7a /tmp/ndk-$USER/src

 # apk
  android update project -p . -s -t android-17
  ../../ndk-build SYSTEM_PREBUILT_PACKAGE=false APP_STL=stlport_static -B APP_ABI=armeabi-v7a
  ant debug -Dasset.dir=prebuilts/assets/armeabi-v7a

 # likewise for armeabi,x86,mips

Change-Id: I166abbd8d1ca08a4e567fcfbfa41262a8d05ddaa

where __i686__ isn't defined

Change-Id: I978fdfa6b93e7e3694b382d2c3ef7cdb9c40e6dc

Change-Id: I052eed49d5376d08fb1aa161fb2d7f8b0c2f45d2

In windows *-gdb.exe is a wrapper which setup up PATH and PYTHONHOME
to python prebuilt directory before calling into the real *-gdb-orig.exe.

For 32-bit windows, i686-w64-mingw32-gcc is used to compile gdb stub
because the default i586-mingw32msvc doesn't have functions such as
CreateJobObject used in the stub.  Problem is that i686-w64-mingw32-gcc
may not be installed in build system and the build script fails silently,
causing 32-bit *-gdb.exe fail to launch due to missing libpython2.7.dll.

This patch is to issue error when stub can't be generated for
whatever reason.

Change-Id: I6c939728aa7d90eafc60cb5637b598092557b584

under "-W -Wall -Wno-unused-parameter"

Change-Id: I3a1bb9ca752b9c2e0ca239889d87c3d513d989c0

* changes:
  ndk-gdb.py: Fix ndk_bin_path determination
  ndk-gdb.py: Handle quoted paths in find_program

It wasn't correct on 64bit. This meant that the gnumake
found on those systems tended to be the system one.

Now, sys.executable is used and if that fails, some more
exhaustive checks of platform.platform() and sys.maxsize
are used (in-case the user uses their own Python - note
if this happens, arch differences between that Python and
the NDK could still cause the system make to be used, but
this is a small corner case that will usually work ok ..)

The quotes in os.environ['PATH'] need to be removed
otherwise executables are not found.

The operator new() doesn't return in regular fashion.
Add __builtin_unreachable() to tell clang otherwise it complains:

  .../ndk/sources/cxx-stl/gabi++/src/new.cc
  .../ndk/sources/cxx-stl/gabi++/src/new.cc:76:1: warning: control may reach
       end of non-void function [-Wreturn-type]

Change-Id: I3179228f89423fc71c81c0eb5686379dd4f95c53

Change-Id: Ia63ab248b91906c0c3b782faf92569f6e1fd3926

.. in build/tools/prebuilt-common.sh, --ldflags is passed
without the $ in-front of HOST_LDFLAGS so that ends up as
the first parameter the wrapper passes to the real ld.

Now it is possile to test llvm-libc++ in a batch each for
different device, eg.

ADB="adb -s emulator-5554" \
  PATH=$PATH:/t/ndk-arm/bin:/t/ndk-mips/bin:/t/ndk-x86/bin \
      ./testit_android --abi=armeabi-v7a

ADB="adb -s emulator-5556" \
  PATH=$PATH:/t/ndk-arm/bin:/t/ndk-mips/bin:/t/ndk-x86/bin \
      ./testit_android --abi=x86

ADB="adb -s emulator-5558" \
  PATH=$PATH:/t/ndk-arm/bin:/t/ndk-mips/bin:/t/ndk-x86/bin \
      ./testit_android --abi=mips

Change-Id: I10634fc9b8b119848cfa159cfe607f87321f9dc0

1. Fixed to create bin/$TOOLCHAIN_PREFIX-clang[++] in addition to
   bin/clang[++]
2. Fixed to rebuild stlport inside /tmp/ndk-$USER
3. Adjusted gcc local patch after 4.8.1 and mclinker rebase
4. Uncomment "@echo off" in find-win-host.cmd
5. Cleanup compiler-rt subdir
6. Use wine 1.7 for 64-bit testing

standalone toolchain

Change-Id: I7e74c4b67c81b2f7276e466c2899037cd100d73a

Change-Id: I7e447b787870e0cb11f75fc2d8bdd2706779c179

Previously GCC disable --eh-frame-hdr for static executable.
Android needs --eh-frame-hdr at least for X86 and MIPS which use
eh frames.

See
1. example: 23e3137e
2. patch for 4.8 https://android-review.googlesource.com/#/c/63181
3. backport to 4.6/4.7: https://android-review.googlesource.com/#/c/63182

Change-Id: I07e0d6a6388068c573f873e2cf2f9a687d271b13

Also add a comment about using 2.23 even for x86_64-4.7 which allow
gold to be built

Change-Id: Ie40b7bbefa5a4b02765fe403b72827f35add32af