strchr interceptor does not need to call strlen if strict_string_checks is not
enabled. Unnecessary strlen calls affect python parser performance.
Details
Details
- Reviewers
kcc eugenis - Commits
- rG9703df2b360a: [asan] Optimize strchr for strict_string_checks=false
rGf50f97c9dd7f: [asan] Optimize strchr for strict_string_checks=false
rCRT301027: [asan] Optimize strchr for strict_string_checks=false
rCRT300889: [asan] Optimize strchr for strict_string_checks=false
rL301027: [asan] Optimize strchr for strict_string_checks=false
rL300889: [asan] Optimize strchr for strict_string_checks=false
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
test/asan/TestCases/strchr_strict.c | ||
---|---|---|
51 ↗ | (On Diff #95988) | Returning a PROT_NONE page to the allocator sounds dangerous. Switch to mmap? |
Comment Actions
There's some Darwin failures: http://green.lab.llvm.org/green/job/clang-stage1-cmake-RA-expensive/5975/