On 30 September 2014 at 19:08, Konstantin Serebryany <konstantin.s.serebry...@gmail.com> wrote: > Correct, you can run tests from llvm tree with any compiler. > https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerTestSuite >
I've read that document, and as a first step I wanted to build LLVM + run the tests in the "best case" (before any modifications I could make, and to have a reference to compare with GCC). I have a few questions. To have clang as the "toolchain I want to test", I added the clang sources under llvm_tmp_src/tools, and compiler-rt sources under projects. I managed to run the tests, but I couldn't find the detailed logs. I added -DLLVM_LIT_ARGS=-v when calling cmake, which gave me a list like: XFAIL: AddressSanitizer64 :: TestCases/use-after-scope.cc (245 of 249) PASS: AddressSanitizer64 :: TestCases/use-after-poison.cc (246 of 249) 1- I suppose there are more details, like gcc.log. Where are they? 2- this is running x86_64 native tests, how can I cross-test with aarch64 (using qemu for instance)? Thanks > Note that lsan does not depend on the compiler, it is a library-only feature. > > --kcc > > On Tue, Sep 30, 2014 at 9:47 AM, Yury Gribov <y.gri...@samsung.com> wrote: >> On 09/30/2014 07:15 PM, Christophe Lyon wrote: >>> >>> Hello, >>> >>> After I've recently enabled Address Sanitizer for AArch64 in GCC, I'd >>> like to enable Leak Sanitizer. >>> >>> I'd like to know what are the requirements wrt testing it? IIUC there >>> are no lsan tests in the GCC testsuite so far. >>> >>> Should I just test a few sample programs to check if basic functionality >>> is OK? >>> >>> The patch seems to be a 1-line patch, I just want to check the >>> acceptance criteria. >> >> >> AFAIK compiler-rt testsuite supports running under non-Clang compiler. Don't >> ask me how to setup the beast though. >>
