similar to: [LLVMdev] Test suite with other compilers

On Jun 30, 2011, at 5:20 AM, Renato Golin wrote: > Hi All, > > Is it possible to run the test-suite with another compiler that it's > not llvm-gcc? I use --with-built-clang --with-llvmcc=clang --with-llvmcxx=clang++ --without-llvmgcc --without-llvmgxx on llvm configure line to use clang built within tree. I checkout clang sources inside my llvm/tools folder. - Devang >

Hi, I'm trying to test the llvm tools as described in 'http://llvm.cs.uiuc.edu/docs/TestingGuide.html'. However, when running the command: 'make check VERBOSE=1 2>&1' I get this error: ------------------- if test -d "/C/projects/build/MinGW/llvm-2-1/test" ; then \ if test -f "/C/projects/build/MinGW/llvm-2-1/test/Makefile" ; then \ echo

On Fri, 7 Jan 2005, Henrik Bach wrote: > I'm trying to test the llvm tools as described in > 'http://llvm.cs.uiuc.edu/docs/TestingGuide.html'. The problem here is that your PATH envvar has spaces in it. There are many thing in LLVM that won't work with that, please try pruning your PATH and trying again. Thanks, -Chris > However, when running the command: 'make

On 11/08/2010 03:18 PM, Duncan Sands wrote: > Hi Tobias, > >> I am very interested in using dragonegg as a fortran frontend for the >> LLVM test >> suite, as a start to improve fortran support. >> >> I believe this should be easy, but when I looked into this I had the >> impression >> the nightly tester in the llvm test-suite does not even support

Now, I've no spaces in my path: ------------------ $ echo $PATH .:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread ------------------ I've found that you safely can delete site.exp. The new values in site.exp are: ------------------ ## these variables are automatically generated by make ## # Do not edit here.

After following all steps from http://llvm.org/docs/TestingGuide.html#testsuiterun, I've got this: make[1]: Entering directory `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource' make[2]: Entering directory `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource/UnitTests' make[3]: Entering directory

Hi Tobias, > I committed an extended version of that patch to llvm core and the test suite. > Can you have a look, if it works for you. if I configure like this then the configure script thinks llvm-gcc is not dragonegg: configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" --with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so" There are several reasons for

You're right. And no errors or results where generated: -------------------- if test -d "/C/projects/build/MinGW/llvm-2-1/test" ; then \ if test -f "/C/projects/build/MinGW/llvm-2-1/test/Makefile" ; then \ echo llvm[0]: Running test suite ; \ make -C /C/projects/build/MinGW/llvm-2-1/test check-local \ TESTSUITE= ; \ else \ echo llvm[0]: No Makefile in

On Fri, 7 Jan 2005, Henrik Bach wrote: > "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread > llvm-gcc" > set llvmgxx >

Could dwarfdump --verify be used to check the debug info? - Jan ________________________________ From: Devang Patel <dpatel at apple.com> To: Talin <viridia at gmail.com> Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Sent: Thu, March 17, 2011 9:41:10 AM Subject: Re: [LLVMdev] Writing unit tests for DWARF? Talin, If there is a magic wand, I would be interested

Hi all, Our buildbot at: http://google1.osuosl.org:8011/ has been upgraded (it is also now linked from the front page). It has a number of handy new features: 1. I imported the 'console' view used by Chromium into our version of buildbot. You can see it here: http://google1.osuosl.org:8011/console This is experimental, but it seems to work well and once you learn to read it it is

Talin, If there is a magic wand, I would be interested to know! DIDescriptor.Verify() is not suitable for you needs. It checks structure of encoded debug info after optimizer has modified the IR. Its main goal is inform Dwarf writer, at the end of code gen, which IR construct it should ignore. If you want to test code gen you have to link compiled code and run it regularly. That's what

On Fri, 7 Jan 2005, Henrik Bach wrote: > You're right. And no errors or results where generated: > PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:/C/projects/src/llvm-2/llvm/test/Scripts:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread > \ > true runtest > make[1]: Leaving directory

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

> LLVM tools and LLVM-GCC I've built seem to work. > Can it be due to LLVM_SRC_ROOT == LLVM_OBJ_ROOT? No. This is usually due to absence of llvm-gcc. You need reconfigure llvm once again with lvm-gcc path added and make sure it was hooked properly (look into Makefile.config for paths, etc). -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

I attempt install and use qmtest for run LLVM testsuit at FreeBSD, but without success. I have installed qm-2.2 (latest and single version accessable from http://www.codesourcery.com/qmtest/download.html in sources) When I start qmtest for LLVM ("make qmtest" in <llvm-obj-dir>/test directory - right?) error printed: ---8X---------------

Hello, After I try making a clean build and got the following error: llvm[3]: Compiling EDDisassembler.cpp for Release build In file included from /llvm/include/llvm/Target/TargetSelect.h:38, from /llvm/lib/MC/MCDisassembler/EDDisassembler.cpp:37: /llvm/stage1/include/llvm/Config/AsmPrinters.def: In function ‘void LLVMInitializeX86TargetAsmPrinter()’:

Ok thanks I'll try that. I was trying to avoid re-building llvm-gcc. Garrison On Dec 10, 2010, at 12:12, Bob Wilson wrote: > > On Dec 10, 2010, at 6:11 AM, Garrison Venn wrote: > >> Hey Chris, >> >> Ok, so I'm working on creating this trivial patch, for starters, but I'm trying to identify >> a controlled unit test for tblgen. So all of the

LLVMers, If you're not working from the CVS "head", you can ignore this. Otherwise, please read it! I have committed changes to CVS head that require changes to your build environment. This is part of PR432. The changes involve getting the CFE to build an executable named llvm-gcc instead of gcc. The hyphenated name was chosen to be consistent with other LLVM tools, it is also

On Tuesday 21 July 2009 12:01, Daniel Dunbar wrote: > 6. Configure style builders now use --without-llvmgcc and > --without-llvmgxx to avoid problems with failing Frontend tests. In > the longer term we should add builders which build llvmgcc and do not > have this problem. I have a builder that does this today. When are you checking your stuff into the LLVM repository? I'd