search for: adttest

...t 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 do not know...

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: <http://lists.llvm.org/piperma...

.... [ 1412s] [ FAILED ] 1 test, listed below: [ 1412s] [ FAILED ] BitVectorTest/0.TrivialOperation, where TypeParam = <type> [ 1412s] [ 1412s] 1 FAILED TEST [ 1412s] [ 1412s] ******************** [ 1412s] Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. [ 1412s] FAIL: LLVM-Unit :: ADT/ADTTests/BitVectorTest/1.TrivialOperation (8457 of 9252) [ 1412s] ******************** TEST 'LLVM-Unit :: ADT/ADTTests/BitVectorTest/1.TrivialOperation' FAILED ******************** [ 1412s] Note: Google Test filter = BitVectorTest/1.TrivialOperation [ 1412s] [==========] Running 1 test from 1 test...

Hi, I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on Windows 7 using MinGW. From there, I thought I would run the tests located under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass without any problem, except for JITTests which fails on the MultiJitTest.JitPool test: [==========] Running 25 tests from 6 test cases. [----------] Global test environment set-up. [--...

2011/11/18 Alan Garny <alan.garny at dpag.ox.ac.uk>: > I have successfully built a shared version of LLVM (both 3.0rc4 and 2.9) on > Windows 7 using MinGW. From there, I thought I would run the tests located > under unittests (i.e. ADTTests, AnalysisTests, ExecutionEnginetests, > JITTests, SupportTests, UtilsTests and VMCoreTests). All of them pass > without any problem, except for JITTests which fails on the > MultiJitTest.JitPool test: > [ RUN      ] MultiJitTest.JitPool > > MultiJITTest.cpp:164: Failure > &gt...

AIX 7.1 & Power5 I have downloaded the llvm source and ran the following steps: 1. ./configure --enable-targets=powerpc 2. gmake Apart from it, i had to make a few changes. i. dladdr code has been commented for the time being and using the default constructor code for that method ii. In Makefile.config, 2 changes were done. +153 # Linker flags. +154 LDFLAGS+=-Wl,-G,-bexpfull +211

...9;. gmake[1]: Leaving directory `/llvm/build/tools/llvm-config' gmake[1]: Entering directory `/llvm/build/unittests' gmake[2]: Entering directory `/llvm/build/unittests/ADT' gmake[2]: *** No rule to make target `/llvm/build/unittests/lib/libLLVMSupport.a', needed by `Release+Asserts/ADTTests'. Stop. gmake[2]: Leaving directory `/llvm/build/unittests/ADT' gmake[1]: *** [ADT/.makeall] Error 2 gmake[1]: Leaving directory `/llvm/build/unittests' gmake: *** [all] Error 1 # Again, we can see that it is looking for "/llvm/build/unittests/lib/libLLVMSupport.a" library...

...iling TwineTest.cpp for Release+Asserts build llvm[2]: Compiling VariadicFunctionTest.cpp for Release+Asserts build llvm[2]: Compiling ilistTest.cpp for Release+Asserts build gmake[2]: *** No rule to make target `/usr/llvm/llvm-3.1.src/unittests/lib/libLLVMSupport.a', needed by `Release+Asserts/ADTTests'. Stop. gmake[2]: Leaving directory `/usr/llvm/llvm-3.1.src/unittests/ADT' gmake[1]: *** [ADT/.makeall] Error 2 gmake[1]: Leaving directory `/usr/llvm/llvm-3.1.src/unittests' gmake: *** [all] Error 1 # cd /usr/llvm/llvm-3.1.src/unittests/ADT # gmake gmake: *** No rule to make target `...

...elow: > [ 1412s] [ FAILED ] BitVectorTest/0.TrivialOperation, where TypeParam = > <type> > [ 1412s] > [ 1412s] 1 FAILED TEST > [ 1412s] > [ 1412s] ******************** > [ 1412s] Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. > [ 1412s] FAIL: LLVM-Unit :: ADT/ADTTests/BitVectorTest/1.TrivialOperation > (8457 of 9252) > [ 1412s] ******************** TEST 'LLVM-Unit :: > ADT/ADTTests/BitVectorTest/1.TrivialOperation' FAILED ******************** > [ 1412s] Note: Google Test filter = BitVectorTest/1.TrivialOperation > [ 1412s] [==========] Ru...

On 10/23/2012 12:20 PM, Sunil Saggar wrote: > I was able to process further by making some code changes and replacing > export-dynamic with -bexpfull in Makefile.config. Now, i am getting > following error while linking .. > > llvm[3]: Linking Release+Asserts Loadable Module LLVMHello.so What exactly was the linking command? -Krzysztof -- Qualcomm Innovation Center, Inc. is a

...b/System But, a new error is appeared llvm[2]: Linking Debug unit test ADT d:/objs/llvm/msys/Debug/lib/libLLVMSystem.a(Process.o):e:/Downloads/llvm-trunk/lib/System/Win32/Process.inc:78: undefined reference to `GetProcessMemoryInfo at 12' collect2: ld returned 1 exit status make[2]: *** [Debug/ADTTests.exe] Error 1 make[2]: Leaving directory `/d/objs/llvm/msys/unittests/ADT' make[1]: *** [ADT/.makeall] Error 2 make[1]: Leaving directory `/d/objs/llvm/msys/unittests' make: *** [all] Error 1 I don't know why, And Pijnacker, do you get the same error? -------------- next part --------...

Hi Since the buildbot host was updated to Fedora F20 levels, the clang buildbot has been failing with the following: $ /home/clangbuild/clang-ppc64-1/lnt.venv/bin/lnt runtest --verbose --submit http://llvm.org/perf/submitRun --commit=1 nt --sandbox nt --no-timestamp --cc /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang --cxx /home/clangbuild/clang-ppc64-1/llvm.install.1/bin/clang++

...^ > [ 1314s] <stdin>:91:13: note: possible intended match here > [ 1314s] 0x000000b7: DW_TAG_lexical_block [8] * > [ 1314s] ^ > [ 1314s] > [ 1314s] -- > > > and > > [ 1314s] ******************** TEST 'LLVM-Unit :: > ADT/ADTTests/HashingTest.HashCombineBasicTest' FAILED ******************** > [ 1314s] Note: Google Test filter = HashingTest.HashCombineBasicTest > [ 1314s] [==========] Running 1 test from 1 test case. > [ 1314s] [----------] Global test environment set-up. > [ 1314s] [----------] 1 test from...

----- Original Message ----- > From: "İsmail Dönmez" <ismail at donmez.ws> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Monday, May 12, 2014 7:18:48 AM > Subject: Re: Lots of regtest failures on PPC64/Linux > > > Hi Hal, > > > > > > On

Wow, I also meet this error before, I'll be pleasure if anyone can solve this problem, and by the way, are you using msys as the building env? It's seems that mingw/cmake is working but mingw/msys, and I didn't ever try with mingw/cygwin:) thanks. 2009/10/1, Ronald Pijnacker <pijnacker at dse.nl>: > Hi all, > > When I try to build llvm on windows/mingw32, I get the

On Thu, Oct 25, 2012 at 01:24:23PM -0700, sunilsaggar wrote: > I am trying to compile llvm in AIX 7.1 machine.. > > I was able to run "gmake libs-only" and it worked well. However, gmake > failed with the following error .. > > # pwd > /usr/llvm/llvm-3.1.src/tools ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ seems you're building in the source tree? Please note that LLVM

Hi all, When I try to build llvm on windows/mingw32, I get the following error: In file included from c:/work/mingw/src/llvm/lib/System/Signals.cpp:33: c:/work/mingw/src/llvm/lib/System/Win32/Signals.inc: In function 'LONG LLVMUnhandledExceptionFilter(_EXCEPTION_POINTERS*)': c:/work/mingw/src/llvm/lib/System/Win32/Signals.inc:275: error: exception handling disabled, use -fexceptions to

I am trying to compile llvm in AIX 7.1 machine.. I was able to run "gmake libs-only" and it worked well. However, gmake failed with the following error .. # pwd /usr/llvm/llvm-3.1.src/tools #gmake gmake[2]: Leaving directory `/usr/llvm/llvm-3.1.src/tools/llvm-config' gmake[2]: Entering directory `/usr/llvm/llvm-3.1.src/tools/opt' gmake[2]: *** No rule to make target

On Tue, May 23, 2017 at 2:40 PM Reid Kleckner <rnk at google.com> wrote: > We have the LLVM_DISABLE_CRASH_REPORT environment variable, but that's > more about whether we should do crash reporting or not. > > It would be pretty reasonable to have another one to disable all this > stuff. It would also be reasonable to have a cmake option that compiles > this stuff away,

...nittests/CMakeFiles 4.0K build/unittests/Bitcode/CMakeFiles/BitcodeTests.dir 4.0K build/unittests/BinaryFormat/CMakeFiles/BinaryFormatTests.dir 4.0K build/unittests/AsmParser/CMakeFiles/AsmParserTests.dir 4.0K build/unittests/Analysis/CMakeFiles/AnalysisTests.dir 4.0K build/unittests/ADT/CMakeFiles/ADTTests.dir 4.0K build/tools/xcode-toolchain/CMakeFiles 4.0K build/tools/polly/unittests/Support/CMakeFiles/ISLToolsTests.dir 4.0K build/tools/polly/unittests/ScopPassManager/CMakeFiles/ScopPassManagerTests.dir 4.0K build/tools/polly/unittests/ScheduleOptimizer/CMakeFiles/ScheduleOptimizerTests.dir 4.0K b...