search for: irtest

...um(int a, int b) { return a + b; } Here, one can produce few mutants: int sum(int a, int b) { return a * b; } int sum(int a, int b) { return a; } Both mutants will uncover that the test is not exhaustive enough. Mutations ### Our Results We run our tool against two test targets from LLVM: IRTests and ADTTests. Based on our setup mutation score for them equals 43% and 66%, correspondingly. We did not analyze all the results thoroughly, yet, but we plan to do so. At the very moment, it is not clear for us how to process the data more efficiently. Also, it is a bit more complicated, since we...

I'm not sure what LLVM_ENABLE_THREADS impacts - whether it is LLVM executables themselves or LLVM-generated code - but it seems to be on by default on the Windows CMake build (I'm building LLVM+Clang at trunk head using CMake/Visual Studio 2013 Win64). But 3 unit tests in IR, which are compiled only if define LLVM_ENABLE_THREADS is set, fail if LLVM_ENABLE_THEADS=ON:

Hello everyone, Are there any reasons the unittests in LLVM repo are split into independent executables, e.g. ADTTests, AnalysisTests, etc. Are there any performance or easy-to-use reasons for this? I plan to migrate to GTest from a project where we have all unittests in a single executable. - Paweł -------------- next part -------------- An HTML attachment was scrubbed... URL:

...to understand the Depth Based Search algorithm in detail -- grasping the main idea behind it should be enough. If you want to have some rough idea on how it works you can try to run domtree tests with -debug-only=dom-tree-builder. To run just the IR tests for dominators, you can do: ./unittests/IR/IRTests --gtest_filter=DominatorTree*. Additionally, you can also play with Holder.F->viewCFG() and DT->viewGraph() to see what's going on inside the tests. I am wondering if there are some other bugs or materials I can go over > in order to achieve a better understanding on the LLVM’s codeb...

Hi, I found that building LLVM in single-threaded mode with CMake is failing because some object files still have references to pthread routines. There are two instances of the build failure happening. $ cmake .../llvm/ -DLLVM_ENABLE_THREADS=0 $ make -j8 check-all % Linking CXX executable IRTests ../../lib/libgtest.a(gtest.cc.o): In function `testing::internal::ThreadLocal<testing::TestPartResultReporterInterface*>::~ThreadLocal()': gtest.cc:(.text._ZN7testing8internal11ThreadLocalIPNS_31TestPartResultReporterInterfaceEED2Ev[_ZN7testing8internal11ThreadLocalIPNS_31TestPartResultR...

Hello, I’m an undergraduate student studying CS in the South China University of Technology. I have been using clang compiler and related tools since I started studying C++ and I would like to work on LLVM in this year’s GSoC. I am interested in “Implement a single updater class for Dominators”. [1] I have achieved a bronze medal in the 2017 ACM-ICPC Asia Xian Regional Contest [2] (being a

...the Depth Based Search algorithm in detail -- grasping the main > idea behind it should be enough. If you want to have some rough idea on how > it works you can try to run domtree tests with -debug-only=dom-tree-builder. > To run just the IR tests for dominators, you can do: ./unittests/IR/IRTests > --gtest_filter=DominatorTree*. Additionally, you can also play with > Holder.F->viewCFG() and DT->viewGraph() to see what's going on inside the > tests. > >> I am wondering if there are some other bugs or materials I can go over >> in order to achieve a better u...

...gt; > idea behind it should be enough. If you want to have some rough idea on >> > how >> > it works you can try to run domtree tests with >> > -debug-only=dom-tree-builder. >> > To run just the IR tests for dominators, you can do: >> > ./unittests/IR/IRTests >> > --gtest_filter=DominatorTree*. Additionally, you can also play with >> > Holder.F->viewCFG() and DT->viewGraph() to see what's going on inside >> > the >> > tests. >> > >> >> I am wondering if there are some other bugs or mate...

...detail -- grasping the > main > > idea behind it should be enough. If you want to have some rough idea on > how > > it works you can try to run domtree tests with > -debug-only=dom-tree-builder. > > To run just the IR tests for dominators, you can do: > ./unittests/IR/IRTests > > --gtest_filter=DominatorTree*. Additionally, you can also play with > > Holder.F->viewCFG() and DT->viewGraph() to see what's going on inside the > > tests. > > > >> I am wondering if there are some other bugs or materials I can go over > >>...

...be enough. If you want to have some rough idea > on > >> > how > >> > it works you can try to run domtree tests with > >> > -debug-only=dom-tree-builder. > >> > To run just the IR tests for dominators, you can do: > >> > ./unittests/IR/IRTests > >> > --gtest_filter=DominatorTree*. Additionally, you can also play with > >> > Holder.F->viewCFG() and DT->viewGraph() to see what's going on inside > >> > the > >> > tests. > >> > > >> >> I am wondering if the...

...ough idea >> >> > on >> >> > how >> >> > it works you can try to run domtree tests with >> >> > -debug-only=dom-tree-builder. >> >> > To run just the IR tests for dominators, you can do: >> >> > ./unittests/IR/IRTests >> >> > --gtest_filter=DominatorTree*. Additionally, you can also play with >> >> > Holder.F->viewCFG() and DT->viewGraph() to see what's going on inside >> >> > the >> >> > tests. >> >> > >> >> >&g...

...0K build/unittests/Object/CMakeFiles/ObjectTests.dir 4.0K build/unittests/MI/CMakeFiles/MITests.dir 4.0K build/unittests/MC/CMakeFiles/MCTests.dir 4.0K build/unittests/Linker/CMakeFiles/LinkerTests.dir 4.0K build/unittests/LineEditor/CMakeFiles/LineEditorTests.dir 4.0K build/unittests/IR/CMakeFiles/IRTests.dir 4.0K build/unittests/FuzzMutate/CMakeFiles/FuzzMutateTests.dir 4.0K build/unittests/ExecutionEngine/Orc/CMakeFiles/OrcJITTests.dir 4.0K build/unittests/ExecutionEngine/MCJIT/CMakeFiles/MCJITTests.dir 4.0K build/unittests/ExecutionEngine/JITLink/CMakeFiles/JITLinkTests.dir 4.0K build/unittests/...