Hi, I've made a simple patch to allow running LLVM's test suite under valgrind. By default it doesn't do any memory leak checking because valgrind reports problems in most tests.. To run the tests with valgrind one has to run 'cd test && make VG=1', similar with what we have with clang. So is this patch ok and/or desirable? Regards, Nuno P.S.: Warning: it takes a loong time to run all the tests with valgrind. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: llvm_test_valgrind.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20081001/b2c4426e/attachment.txt>
In case someone is interested in trying out the patch, I've updated it a bit and posted it at http://web.ist.utl.pt/nuno.lopes/llvm_test_valgrind.txt Nuno ----- Original Message -----> Hi, > > I've made a simple patch to allow running LLVM's test suite under > valgrind. > By default it doesn't do any memory leak checking because valgrind reports > problems in most tests.. > To run the tests with valgrind one has to run 'cd test && make VG=1', > similar with what we have with clang. > > So is this patch ok and/or desirable? > > Regards, > Nuno > > P.S.: Warning: it takes a loong time to run all the tests with valgrind.
Possibly Parallel Threads
- [LLVMdev] missed optimizations
- Alive now available online
- [LLVMdev] missed optimizations
- Why SI.isSigned() is not equals to E->getType()->isSignedIntegerOrEnumerationType()?
- error: ordered comparison between pointer and zero ('address' (aka 'unsigned char *') and 'int')