[asan][test] Disable inner string interceptors on android-37 in strpbrk-2.c and strtok.c (#235588) These tests disable `intercept_strpbrk` or `intercept_strtok` via `ASAN_OPTIONS` and expect `strict_string_checks=true` to still catch out-of-bounds reads via the underlying `strcspn`/`strspn` calls inside `libc`. On Android API 37 (`x86_64`), Bionic moved `strspn` and `strcspn` out of `libc/bionic/string.cpp` into `libc/portable-simd/strspn.cpp` (https://android.googlesource.com/platform/bionic/+/a11b70b3b16b09d3384056d2a0f093d0a09eb182 for `x86_64`, https://android.googlesource.com/platform/bionic/+/72bc53739 for `arm64`, and https://android.googlesource.com/platform/bionic/+/382ae7c425e8b315b83d63439b98b2b8832accdd): - `strpbrk` and `strtok` in `libc/bionic/string.cpp` no longer inline `strspn`/`strcspn` and instead call them via the PLT (`strspn@plt`, `strcspn@plt`). - `libc/portable-simd/strspn.cpp` dispatches single-character `strcspn` calls to `strchrnul@plt` (controlled by `intercept_strchr`) and empty-delimiter `strcspn` calls to `__strlen_chk@plt` (controlled by `intercept_strlen`). On `android-37`, also set `intercept_strspn=false`, `intercept_strchr=false`, and `intercept_strlen=false` in `strtok.c` (and `intercept_strspn=false` in `strpbrk-2.c`) so the negative `!not` runs exercise the unintercepted fallback path as intended. Fixes failures on https://lab.llvm.org/buildbot/#/builders/sanitizer-x86_64-linux-android. Assisted-by: Gemini
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.