Re: Test suite run time
Posted by
Peter Caspers-4 on
Nov 27, 2015; 5:31pm
URL: http://quantlib.414.s1.nabble.com/Test-suite-run-time-tp17128p17134.html
Hello,
to give a benchmark, it takes around 8h to run memcheck on the whole test-suite, which means a slow-down factor of approximately 50x. This is with -O3 though, which may hide or produce bogus uninitialized value errors under certain (but rare) circumstances (according to the valgrind documentation). Since its diagnostics concerning memory errors seems pretty much exhaustive (it is e.g. comparable to clang's address + memory + leak sanitizer), I am wondering what Visual Studio is (thinking it is) doing? Is it turning off optimization maybe? Or is it doing something in the direction of thread-safety?
Is it possible to switch optimization levels, debug symbol generation and sanitizing code instrumentation separately from each other in the studio? If yes, one can maybe find a viable compromise for these settings between running time and error sensitivity depending on what exactly one is expecting.
Peter
------------------------------------------------------------------------------
_______________________________________________
QuantLib-dev mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-dev