search for: r270937

...RAGE=1 -DLLVM_USE_SANITIZER=Address -DCMAKE_BUILD_TYPE=RELEASE ../src/ && make check-fuzzer -j8 ``` where ``<new_clang>`` and ``<new_clang++>`` point to a recently built clang (llvm: r270960 , clang: r270962 , compiler-rt: r270949) which itself was compiled using gcc 6.1.1. In r270937 (prior commit) the time to run the tests was ~25 seconds on my machine but for the subsequent commit ( r270942 ) the tests took ~78 seconds. If I run the tests ``` cd lib/Fuzzer/test python2 ../../../bin/llvm-lit -v --time-tests -j1 . ``` then I can observe the time it is taking to run the tests...

...CMAKE_BUILD_TYPE=RELEASE ../src/ && > make check-fuzzer -j8 > ``` > > where ``<new_clang>`` and ``<new_clang++>`` point to a recently built > clang (llvm: r270960 , clang: r270962 , compiler-rt: r270949) which > itself was compiled using gcc 6.1.1. > > In r270937 (prior commit) the time to run the tests was ~25 seconds on > my machine but for the subsequent commit ( r270942 ) the tests took > ~78 seconds. > > If I run the tests > > ``` > cd lib/Fuzzer/test > python2 ../../../bin/llvm-lit -v --time-tests -j1 . > ``` > > then...

...&& >> make check-fuzzer -j8 >> ``` >> >> where ``<new_clang>`` and ``<new_clang++>`` point to a recently built >> clang (llvm: r270960 , clang: r270962 , compiler-rt: r270949) which >> itself was compiled using gcc 6.1.1. >> >> In r270937 (prior commit) the time to run the tests was ~25 seconds on >> my machine but for the subsequent commit ( r270942 ) the tests took >> ~78 seconds. >> >> If I run the tests >> >> ``` >> cd lib/Fuzzer/test >> python2 ../../../bin/llvm-lit -v --time-test...