similar to: GTest: Unit tests layout

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:

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,

Hello, everybody. We are working on a tool for mutation testing. The work is still in progress and far away from being done. However, we have got some results already. And we would like to share them with you. But, let me give you a brief introduction first. ### Mutation Testing In a nutshell, Mutation Testing is a way to evaluate a quality of a test suite. The approach suggests introducing a

Hi, Using openSUSE 13.1 on s390x machine I get two new regressions with llvm 3.4rc1: [ 1412s] /home/abuild/rpmbuild/BUILD/llvm/unittests/ADT/BitVectorTest.cpp:39: Failure [ 1412s] Value of: Vec.count() [ 1412s] Actual: 1 [ 1412s] Expected: 5U [ 1412s] Which is: 5 [ 1412s] /home/abuild/rpmbuild/BUILD/llvm/unittests/ADT/BitVectorTest.cpp:42: Failure [ 1412s] Value of: Vec.all() [ 1412s]

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:

On Thu, Jan 21, 2016 at 7:04 PM, Brian Cain via cfe-dev < cfe-dev at lists.llvm.org> wrote: > SuSE Linux Enterprise Server 11SP3 x86_64 > > Looks like I see several failures that weren't in 3.7.1. Is there any way > to tell whether these are regressions vs new-to-3.8.0-but-failing? The > MSan ones were in 3.7.1 but the ThreadPoolTest and the libc++ errors were > not

thanks for the reply ..I tried building it from outside ...but got a similar error .. # ls /llvm/src ==> src directory llvm-3.1.src # pwd /llvm/build ==> build directory #gmake libs-only ... ... gmake[2]: Leaving directory `/llvm/build/lib/DebugInfo' gmake[1]: Leaving directory `/llvm/build/lib' gmake[1]: Entering directory `/llvm/build/tools/llvm-config'

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

Here's the failing tests for rc2 on SLES11.3 (glibc 2.11, libstdc++4.7). I've done some amount of triaging what some critical elements of the failures are. Unabridged log is attached. Failing Tests (94): LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncIntInt LLVM-Unit :: ExecutionEngine/Orc/OrcJITTests/DummyRPC.TestAsyncVoidBool LLVM-Unit ::

Well, Now I get the solution. Please, someone can apply the patch. Just modify the makefile resident in lib/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]: ***

Hi! Since a time I had sporadic mysterious link errors in gtest. Now I found the solution: llvm provides its own modified version of gtest but generates lib files of the original names. Therefore please rename the modified gtest libs for example to llvmgtest (libllvmgtest.a and libllvmgtest_main.a) Thanks, -Jochen

$(llvm-config --libs | tr " " "\n" | grep gtest) returns: -lgtest_main -lgtest instead of non-valid: -lLLVMgtest_main -lLLVMgtest It also fixes: $(ld): cannot find -lLLVMgtest $(ld): cannot find -lLLVMgtest_main --- unittests/Makefile.unittest | 2 +- utils/llvm-build/llvmbuild/componentinfo.py | 4 ++-- utils/llvm-build/llvmbuild/main.py |

(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There

Hi, I just tagged 3.9.1-rc2, so testing can begin. There was a bug found in -rc1 before I could send out a release announcement, so I decided to merge the fix and tag -rc2 to save some testing cycles. We can always use more testers, so if you are interested in helping, let me know. Thanks, Tom

missing-abstract-variable is a recent one I introduced - looking into it. On Wed, Jun 4, 2014 at 2:39 AM, İsmail Dönmez <ismail at donmez.ws> wrote: > Hi Hal, > > These tests failures go away when I disable static libs aka > -DBUILD_SHARED_LIBS=OFF , with that only 2 regtest failures are left: > > > [ 1314s] FAILED: cd /home/abuild/rpmbuild/BUILD/llvm/stage2/test

I googled and found that there was a bug raised with similar issue. http://llvm.org/bugs/show_bug.cgi?id=2210 I applied the code changes mentioned in the bug and it worked. Now, i am stuck at the following error. Working overit .. llvm[2]: Compiling SmallVectorTest.cpp for Release+Asserts build llvm[2]: Compiling SparseBitVectorTest.cpp for Release+Asserts build llvm[2]: Compiling

İsmail Dönmez <ismail at donmez.ws> writes: > Using openSUSE 13.1 on s390x machine I get two new regressions with llvm > 3.4rc1: Hmm, I don't see this locally. Just to rule out one possibility, which compiler are you using to build? Do you see the same thing with a -O0 build? Thanks, Richard > [ 1412s] >

----- Original Message ----- > From: "Paweł Bylica" <chfast at gmail.com> > To: "LLVMdev" <llvmdev at cs.uiuc.edu> > Sent: Friday, May 22, 2015 8:45:11 AM > Subject: Re: [LLVMdev] Problems with instruction scheduling > > > > Any comments? Not in particular, but I think we're pretty close to applying a rewrite by Jonas Paulsson

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

----- Original Message ----- > From: "Paweł Bylica" <chfast at gmail.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVMdev" <llvmdev at cs.uiuc.edu>, "Jonas Paulsson" <jonas.paulsson at ericsson.com> > Sent: Friday, May 22, 2015 9:19:14 AM > Subject: Re: [LLVMdev] Problems with instruction scheduling > >