Android NDK for MacR22b

Announcements:

• GNU binutils is deprecated and will be removed in an upcoming NDK release. Note that the GNU assembler (as) is a part of this. If you are building with -fno-integrated-as, file bugs if anything is preventing you from removing that flag. If you're using as directly, use clang instead.
• LLD is now the default linker. ndk-build and our CMake toolchain file have also migrated to using llvm-ar and llvm-strip.
• See the Changes section below for more information.

r22b:

• Issue 1377: Fix Clang backend crash in register scavenging.
• Issue 1388: Fixed LLVM's incorrect conversion to list files for long command lines on Windows.
• Issue 1391: Fixed missing symbols from libz.a.
• Issue 1427: Fixed Clang auto-detection for CMake 3.19 and older for Windows.

Changes:

• Updated LLVM to r399163b, based on LLVM 11 development.
• Issue 829: Fixed issue with __attribute__((visibility("hidden"))) symbols sometimes not being hidden.
• Issue 1149: Fixed Clang crash with #pragma detect_mismatch.
• Issue 1212: Fixed llvm-strip to match GNU behavior for removing file symbols.
• Issue 1248: Fixed LLD Neon crash.
• Issue 1303: Fixed Neon intrinsic optimizer crash.
• Updated make to 4.3.
• Updated libc++, libc++abi, and libunwind to https://github.com/llvm/llvm-project/commit/52ec983895436089c5be0b0c4d967423db16045b.
• Issue 609: std::filesystem support is now included. There are two known issues.
• Issue 1258: std::filesystem::perm_options::nofollow may not be honored on old devices.
• Issue 1260: std::filesystem::canonical will incorrectly succeed when passed a non-existent path on old devices.
• Issue 843: llvm-strip is now used instead of strip to avoid breaking RelRO with LLD. Note that the Android Gradle Plugin performs its own stripping, so most users will need to upgrade to Android Gradle Plugin version 4.0 or newer to get the fix.
• Issue 1130: Fixed undefined references to new that could occur when building for APIs prior to 21 and the static libc++. Note that LLD appears to have been unaffected, but the problem is still present for ndk-build when using the deprecated linkers.
• Issue 1139: native_app_glue now hooks up the APP_CMD_WINDOW_RESIZED, APP_CMD_WINDOW_REDRAW_NEEDED, and APP_CMD_CONTENT_RECT_CHANGED messages.
• Issue 1196: Backtraces for crashes on devices older than API 29 are now correct when using LLD if using ndk-build or the CMake toolchain file. If using a different system and targeting devices older than API 29, use -Wl,--no-rosegment when linking. See the Build System Maintainers Guide for more information.
• The deprecated /platforms and /sysroot directories have been removed. These directories were merged and relocated into the toolchain during r19. The location of these contents should not be relevant to anyone, including build systems, since the toolchain handles them implicitly. If you are using a build system that hasn't adapted to the changes introduced in NDK r19, file a bug with your build system maintainer. See the Build System Maintainers Guide for information on using the NDK in your own build system.
• llvm-ar is now used instead of ar.
• Issue 1200: Fixed an issue with using dlclose with libraries using thread_local with non-trivial destructors and the static libc++.
• The legacy libc++ linker scripts in /sources/cxx-stl/llvm-libc++ have been removed. The linkers scripts in the toolchain should be used instead as described by the Build System Maintainers Guide.
• LLD is now used by default. If your build is not yet compatible with LLD, you can continue using the deprecated linkers, set APP_LD=deprecated for ndk-build, ANDROID_LD=deprecated for CMake, or use an explicit -fuse-ld=gold or -fuse-ld=bfd in your custom build system. If you encounter issues be sure to file a bug, because this will not be an option in a subsequent release.
• Note that Issue 843 will affect builds using LLD with binutils strip and objcopy as opposed to llvm-strip and llvm-objcopy.
• ndk-gdb now uses lldb as the debugger. gdb is deprecated and will be removed in a future release. To fall back to gdb, use --no-lldb option. But please file a bug explaining why you couldn't use lldb.