similar to: [LLVMdev] Running the test-suite

On Apr 10, 3:49 pm, Dominic Hamon <dom.ha... at gmail.com> wrote: > Hello Hi Dominic! > > I spent some time trying to get the test-suite running as per the > instructions here:http://www.llvm.org/docs/TestingGuide.html Yep. > > I was continually getting an error "No rule to make target > `Output/sse.expandfft.linked.rbc', needed by >

I would like to make the following target specific modifications to clang and would like to get some advice from experts. 1) My target supports very poor stack access so we implement "static stack". In this model, all local variables will have static storage class. I think I can take care of this in the clang::CGDecl.cpp::CodeGenFunction::EmitBlockVarDecl() 2) To improve memory usage,

On Sun, Dec 13, 2009 at 11:34 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> 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

Hello, I am new in using llvm so I would like to get some help on how to compile test-suite. Assumptions: llvm is in /llvm directory llvm-gcc is in /llvm-4.2-2.4-x86-linux-RHEL4/bin I have tried compiling test-suite and I get the following error: $make make[1]: Entering directory '/llvm/projects/test-suite/SingleSource' make[2]: Entering directory

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

On Apr 10, 2008, at 10:44 AM, <Alireza.Moshtaghi at microchip.com> <Alireza.Moshtaghi at microchip.com > wrote: > I would like to make the following target specific modifications to > clang and would like to get some advice from experts. Ok. cfe-dev might be more appropriate for clang questions, but... > > 1) My target supports very poor stack access so we implement

Hi, I'm trying to run the tests in llvm-suite, but I've run into trouble. First, I had the llvm-suite checkout in a directory alongside the llvm compiler checkout, but, when I ran "make" from llvm-suite, it complained about there not being a Makefile two levels above it, so I moved llvm-suite into the "test" subdirectory inside the llvm compiler checkout. I ran

Chris, The reasons for not wanting the code generator to modify alloca to global references are: (1) Variable name is not as easily available in the code generator. (2) I did not want to go behind the back of compiler and change the storage class of a variable in the middle of the way. I felt more comfortable to have the frontend generate the correct information to begin with. But it concerns

2009/3/28 John Mosby <ojomojo at gmail.com> > Thanks Duncan, > I figured it out after a couple of tries, but the docs are not as clear as > your instructions. If there's no specific maintainer of TestingGuide.html, > I'd be happy to update the docs to be as clear as your instructions. > > llvm/projects/Makefile filters out "test-suite" and

hello, i've problems running the llvm-test suite using debian linux and make 3.81. it works fine on my laptop, running openSuse and make 3.81. i already tried to install make 3.75 and 3.79, both did not work. the error message is: make[1]: *** No rule to make target `Output/sse.expantfft.bc', needed by `Output/sse.expandfft.linked.rbc'. Stop. using make -p, i see that

> It looks to me that this: > > make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc', > needed by `Output/sse.expandfft.linked.bc'.  Stop. Well, I have no idea then. makefiles of testsuite are well-known for such erratic behavior :( -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

On Sun, Dec 13, 2009 at 8:17 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> It looks to me that this: >> >> make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc', >> needed by `Output/sse.expandfft.linked.bc'.  Stop. > Well, I have no idea then. makefiles of testsuite are well-known for > such erratic behavior :( For the

On Fri, 04 May 2007 14:37:53 +0200 Florian Brandner <fbrandne at mail.tuwien.ac.at> wrote: >hello, > >i've problems running the llvm-test suite using debian linux and make >3.81. it works fine on my laptop, running openSuse and make 3.81. > >i already tried to install make 3.75 and 3.79, both did not work. > >the error message is: > >make[1]: *** No rule to

Reid Spencer wrote: > Have you modified the makefile in any way? Note that sse.expantfft.bc should be sse.expandfft.bc no, did'nt change it. the typo before seems to be an error while copying from the terminal. i've cleaned everything and tried again. this is the messsage: [brandner:/localtmp/brandner/dev/llvm-test:529] make -j1 TEST=nightly 2>&1 | tee report.nightly.raw.out

On Mon, Feb 23, 2009 at 6:32 PM, John Criswell <criswell at cs.uiuc.edu> wrote: > Aaron Gray wrote: > > I am trying to build llvm-test in a separate directory to the main llvm > tree. > > > > I have put llvm and llvm-gcc's bin directories on the path but think I am > missing a switch on the configure command. > > > You need to use --with-llvmsrc and

Hi Gregory, > `/cygdrive/c/projects/thesis/llvm-suite-2.6/llvm-2.6/projects/test-suite/SingleSource/UnitTests/Vector/SSE' > make[4]: *** No rule to make target `Output/sse.expandfft.linked.rbc', this usually means that you don't have llvm-gcc installed, or, if you do have it installed, that the configure script did not find it. Ciao, Duncan.

Thanks Duncan, I figured it out after a couple of tries, but the docs are not as clear as your instructions. If there's no specific maintainer of TestingGuide.html, I'd be happy to update the docs to be as clear as your instructions. llvm/projects/Makefile filters out "test-suite" and "llvm-test" when builds are done, so it looks like those two names work. John On

On Saturday 15 September 2007, Tanya Lattner wrote: > 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source. > Compile everything. Run "make check" and the full llvm-test suite > (make TEST=nightly report). I tried to do this, but ran into trouble. LLVM itself compiled fine. GCC compilation is broken when Java support is enabled. I can file a detailed bug report

I'm trying to run some of the test suite using the instructions here: http://llvm.org/docs/TestingGuide.html#quicktestsuite I've built llvm myself, but I'm using pre-built binaries of llvm-gcc (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). Here's what happens: foad at debian:~/svn/llvm-project/test-suite/trunk$ ./configure

So, when performing expression evaluation, lldb trips over an assert in clang/lib/AST/RecordLayoutBuilder because ExternalFieldOffsets doesn't contain a FieldDecl that updateExternalFieldOffset expected. I found that the assert occurs when both static and non-static member variables are present. For instance, with the following, the lldb command 'expr my_test.length()' does not