search for: testmain

...here's superfluous flags please do tell and I'll remove them. Also is there a flag to skip tests? Is building lld on linux supported? I tried including lld in the build and it failed: llvm[4]: Linking Release unit test CoreTest (without symbols) /tmp/llvm/build/Release/lib/libgtest_main.a(TestMain.o): In function `main': /tmp/llvm/llvm/utils/unittest/UnitTestMain/TestMain.cpp:(.text.main+0x28): undefined reference to `llvm::cl::ParseCommandLineOptions(int, char const* const*, char const*)' clang: error: linker command failed with exit code 1 (use -v to see invocation) /tmp/llvm/llvm/...

+++ unittests/TestMain.cpp (revision 0) +//===--- unittest.cpp - unittest driver -----------------------------------===// +++ unittests/ADT/DenseMapTest.cpp (revision 0) +//===- llvm/unittest/DenseMapMap.h - DenseMap unit tests --------*- C++ -*-===// You probably want to update these file headers to match their...

OK changes made and new patch attached. Comments below: On Tue, Dec 30, 2008 at 2:40 PM, Misha Brukman <brukman at gmail.com> wrote: > +++ unittests/TestMain.cpp (revision 0) > +//===--- unittest.cpp - unittest driver > -----------------------------------===// > > +++ unittests/ADT/DenseMapTest.cpp (revision 0) > +//===- llvm/unittest/DenseMapMap.h - DenseMap unit tests --------*- C++ > -*-===// > > You probably want to upd...

...The makefile target to build and run the tests is "make unittest" (I wasn't sure if you could have a synthetic target that was the same as the name of a directory, so I made it "unittest" instead of "unittests") - There's a common Makefile and a common TestMain.cpp in llvm/unittests. The individual tests are in llvm/unittests/<dir> where <dir> is the name of an LLVM library such as "ADT". Each of these subdirs has a tiny makefile which sets TESTNAME=<name> and then includes the common Makefile.unittest. Each subdir...

...the > name of a directory, so I made it "unittest" instead of "unittests") > > I don't think that's an issue -- to recurse into a directory, you have to say "make -C dir [target]". > > - > - There's a common Makefile and a common TestMain.cpp in > llvm/unittests. The individual tests are in llvm/unittests/<dir> where <dir> > is the name of an LLVM library such as "ADT". Each of these subdirs has a > tiny makefile which sets TESTNAME=<name> and then includes the common > Makefile.un...

...github.com/llvm/llvm-project/tree/master/llvm/utils/KillTheDoctor [2] https://www.ecosia.org/images?q=%22has+stopped+working%22 [3] https://github.com/llvm/llvm-project/blob/master/llvm/lib/Support/Windows/Signals.inc#L484 [4] https://github.com/llvm/llvm-project/blob/master/llvm/utils/unittest/UnitTestMain/TestMain.cpp#L38 [5] https://devblogs.microsoft.com/oldnewthing/20160204-00/?p=92972 [6] https://github.com/llvm/llvm-project/blob/master/compiler-rt/test/lit.common.cfg.py#L219 [7] https://github.com/llvm/llvm-project/blob/master/llvm/utils/not/not.cpp#L48 [8] https://github.com/llvm/llvm-project/...

...d over a number of days. Putting aside issues of the error covariance structure I'm using the simple compound symmetry. The SAS code I'm using is: Proc mixed ; class dose day animal ; model blood=dose|day / htype=1,3; repeated day / subject = animal type = cs; run; and the lme code is testmain<-lme(blood~dose*day, random=~1|animal, data=sasdata, na.action = (na.omit)) anova(testmain) The overall test of the fixed effects agree as expected, but when I tried Blood2 (which has missing data) only the Day*Dose interaction agrees. I tried sequential and marginal options in the anove.lme co...

...please do tell and I'll remove them. > > Also is there a flag to skip tests? > > Is building lld on linux supported? I tried including lld in the build and it failed: > llvm[4]: Linking Release unit test CoreTest (without symbols) > /tmp/llvm/build/Release/lib/libgtest_main.a(TestMain.o): In function `main': > /tmp/llvm/llvm/utils/unittest/UnitTestMain/TestMain.cpp:(.text.main+0x28): > undefined reference to `llvm::cl::ParseCommandLineOptions(int, char > const* const*, char const*)' > clang: error: linker command failed with exit code 1 (use -v to see invocat...

...utils/unittest/googletest/src/gtest.cc:2145 #13 testing::UnitTest::Run (this=<optimized out>) at /home/rengolin/devel/llvm/src/llvm/utils/unittest/googletest/src/gtest.cc:3842 #14 0x0000000000410796 in main (argc=1, argv=0x7fffffffe0d8) at /home/rengolin/devel/llvm/src/llvm/utils/unittest/UnitTestMain/TestMain.cpp:48 > On the cyclic dependency there was a recent conversation that was trying to > fix this, but I am not sure where it is. Is this on llvmdev? Or is there a special lld list? cheers, --renato

Hans, I have posted a complete patch for solving the linkage issues with LLVM_LINK_LLVM_DYLIB on Phabricator at http://reviews.llvm.org/D16945. The bulk of the fix the simple changes of... Index: cmake/modules/AddLLVM.cmake =================================================================== --- cmake/modules/AddLLVM.cmake (revision 259743) +++ cmake/modules/AddLLVM.cmake (working copy) @@

...# Depends on llvm::raw_ostream -) +if (LLVM_LINK_LLVM_DYLIB) + set(LIBS + LLVM # Depends on llvm::raw_ostream + ) +else() + set(LIBS + LLVMSupport # Depends on llvm::raw_ostream + ) +endif() find_library(PTHREAD_LIBRARY_PATH pthread) if (PTHREAD_LIBRARY_PATH) Index: utils/unittest/UnitTestMain/CMakeLists.txt =================================================================== --- utils/unittest/UnitTestMain/CMakeLists.txt (revision 260200) +++ utils/unittest/UnitTestMain/CMakeLists.txt (working copy) @@ -1,7 +1,17 @@ -add_llvm_library(gtest_main - TestMain.cpp +if (LLVM_LINK_LLVM_DYLIB...

Folks, I'm having a look at LLD and I need some guidance... I know it's not production ready for x86 and ARM (the idea is to make it so). My steps: I've added it to tools/lld and ran CMake again (on x86_64) on a standard release build (static linking). It works, builds but I see one unit test error: Note: Google Test filter = InputGraphTest.Observer [==========] Running 1 test from

On Dec 30, 2008, at 2:54 PM, Talin wrote: > OK changes made and new patch attached. Nice +++ utils/unittest/Makefile (revision 0) ... +# This has to come after Makefile.common, since it doesn't allow us to +# override the VPATH value unless we set PROJECT_NAME, which we don't want +# to do. +VPATH = $(LLVM_SRC_ROOT)/utils/unittest/googletest/src/ Why play with VPATH here? What

I'm so close to having LLVM build on PowerPC. If there's any PowerPC experts, help? Lines like this: outs() << "[" << format("%2d", i) << "]" << "(sec " << format("%2d", int16_t(symbol->SectionNumber)) << ")" << "(fl 0x" <<

Hi, You asked for bug reports on failed build/platforms combinations, here is one: —————— . . . llvm[3]: Compiling TestMain.cpp for Debug+Asserts build llvm[3]: Building Debug+Asserts Archive Library libUnitTestMain.a gmake[3]: Leaving directory `/home/jocke/gcd/llvm/utils/unittest/UnitTestMain' gmake[2]: Leaving directory `/home/jocke/gcd/llvm/utils/unittest' gmake[1]: Leaving directory `/home/jocke/gcd/llvm/ut...

...build llvm[2]: Compiling ARMDecoderEmitter.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable count (without symbols) llvm[2]: ======= Finished Linking Release+Asserts Executable count (without symbols) llvm[3]: Compiling gtest.cc for Release+Asserts build llvm[3]: Compiling TestMain.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable not (without symbols) llvm[2]: ======= Finished Linking Release+Asserts Executable not (without symbols) llvm[3]: Compiling gtest-death-test.cc for Release+Asserts build llvm[2]: Linking Release+Asserts executable fpcmp (with...

...iling ARMDecoderEmitter.cpp for Release+Asserts build > llvm[2]: Linking Release+Asserts executable count (without symbols) > llvm[2]: ======= Finished Linking Release+Asserts Executable count (without symbols) > llvm[3]: Compiling gtest.cc for Release+Asserts build > llvm[3]: Compiling TestMain.cpp for Release+Asserts build > llvm[2]: Linking Release+Asserts executable not (without symbols) > llvm[2]: ======= Finished Linking Release+Asserts Executable not (without symbols) > llvm[3]: Compiling gtest-death-test.cc for Release+Asserts build > llvm[2]: Linking Release+Asserts ex...

...s Operation { public: virtual int test_add(int a, int b)=0; virtual int test_sub(int a, int b)=0; }; class A : public Operation { public: int test_add(int a, int b) { return a + b; } int test_sub(int a, int b) { return a - b; } }; A myA; int __attribute__ ((noinline)) testmain(int (A::*fptr)(int, int)) { return (myA.*fptr)(1, 2); } ---------------------------------------------------------------------------- The debugging output of the ICP pass for this example is as follows: ----------------------------------------------------------------------------**** INDIRECT CAL...

...== Finished Linking Release+Asserts Executable not (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/utils/not' llvm[2]: Compiling CodeGenDAGPatterns.cpp for Release+Asserts build make[3]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/utils/unittest/UnitTestMain' llvm[3]: Compiling TestMain.cpp for Release+Asserts build make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/utils/yaml-bench' llvm[2]: Compiling YAMLBench.cpp for Release+Asserts build llvm[3]: Building Release+Asserts Archive Library libgtest_main.a make[3]: Leaving directo...