| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[compiler-rt] [test] Generalize an UNSUPPORTED marking (#168858) Don't specifically target windows-msvc - the same goes for any windows target; mingw doesn't have dlfcn.h either. | 8 个月前 | |
[sanitizer][test] Unify LD_LIBRARY_PATH handling (#111498) When testing on Linux/sparc64 with a runtimes build, the UBSan-Standalone-sparc :: TestCases/Misc/Linux/sigaction.cpp test FAILs: runtimes/runtimes-bins/compiler-rt/test/ubsan/Standalone-sparc/TestCases/Misc/Linux/Output/sigaction.cpp.tmp: error while loading shared libraries: libclang_rt.ubsan_standalone.so: wrong ELF class: ELFCLASS64 It turns out SPARC needs the same LD_LIBRARY_PATH handling as x86. This is what this patch does, at the same time noticing that the current duplication between lit.common.cfg.py and asan/Unit/lit.site.cfg.py.in isn't necessary. Tested on sparc64-unknown-linux-gnu and x86_64-pc-linux-gnu. | 1 年前 | |
[ASan][test] Enable ASan tests on SPARC (#107405) With PR #107223 and PR #107403, ASan testing can be enabled on SPARC. This patch does so, 32-bit only on both Solaris and Linux. There is no 64-bit support even in GCC. Apart from the obvious CMake changes, this patch includes a couple of testcase adjustments necessary for SPARC: - In asan_oob_test.cpp, the OOB_int subtest needs to be disabled: it performs unaligned accesses that cannot work on a strict-alignment target like SPARC. - asan_test.cpp needs to disable subtests that depend on support for __builtin_setjmp and __builtin_longjmp. - zero_page_pc.cpp reports 0x5 as the faulting address on access to 0x4. I don't really know why, but it's consistent between Solaris and Linux. Tested on sparcv9-sun-solaris2.11 and sparc64-unknown-linux-gnu. | 1 年前 | |
[ASan] Make tests work with internal shell Some minor adjustmenets around environment variables to make a handful of tests work with the internal shell that did not before. Reviewers: fmayer, alexander-shaposhnikov Reviewed By: fmayer, alexander-shaposhnikov Pull Request: https://github.com/llvm/llvm-project/pull/165141 | 9 个月前 | |
[sanitizer] Disable fast_unwind_on_malloc as default for arm-linux-gnu ARM thumb/thumb2 frame pointer is inconsistent on GCC and Clang [1] and fast-unwider is also unreliable when mixing arm and thumb code [2]. The fast unwinder on ARM tries to probe and compare the frame-pointer at different stack layout positions and it works reliable only on systems where all the libraries were built in arm mode (either with gcc or clang) or with clang in thmb mode (which uses the same stack frame pointer layout in arm and thumb). However when mixing objects built with different abi modes the fast unwinder is still problematic as shown by the failures on the AddressSanitizer.ThreadStackReuseTest. For these failures, the malloc is called by the loader itself and since it has been built with a thum enabled gcc, the stack frame is not correctly obtained and the suppression rule is not applied (resulting in a leak warning). The check for fast-unwinder-works is also changed: instead of checking f it is explicit enabled in the compiler flags, it now checks if compiler defined thumb pre-processor. This should fix BZ#44158. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92172 [2] https://bugs.llvm.org/show_bug.cgi?id=44158 Reviewed By: eugenis Differential Revision: https://reviews.llvm.org/D88958 | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 8 个月前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 9 个月前 | ||
| 5 年前 |