similar to: [LLVMdev] LLVM test-suite

On Mar 28, 2009, at 12:56 PM, Aaron Gray wrote: > How do I get the LLVM test-suite to work I have followed the /docs/ > TestingGuide.html but cannot seem to get it to work. I have tried > many variations, but get no joy. The docmunetation does not appear > very clear. Some things that are not so obvious: The testsuite has to be checked out as a subdirectory of llvm/ projects;

Thanks for the reply. Do I check it out under src or build directory ? I am sure I had all this working fine with no problems 2 years ago. Aaron ----- Original Message ----- From: Dale Johannesen To: LLVM Developers Mailing List Sent: Saturday, March 28, 2009 8:11 PM Subject: Re: [LLVMdev] LLVM test-suite On Mar 28, 2009, at 12:56 PM, Aaron Gray wrote: How do I get the

Hi Aaron, > How do I get the LLVM test-suite to work I have followed the /docs/TestingGuide.html but cannot seem to get it to work. I have tried many variations, but get no joy. The docmunetation does not appear very clear. (1) check out the testsuite. The default name of the checkout is "test-suite". (2) move it into llvm/projects/, changing the name to llvm-test, so now you have

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

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

2009/3/28 Dale Johannesen <dalej at apple.com>: > The testsuite has to be checked out as a subdirectory of llvm/projects; > llvm/projects/llvmtest or some such. > After doing that, you need to re-configure from the top level.  There must > be a working llvm-gcc in your path when you do this. I've got a makefile that tries to build llvm and llvm-gcc from source, and then run

hello everybody, I would like to improve the llvm-test suite[1] as a part of GSoC 2008 program for LLVM. I have few concerns/problems regarding this, please give me your feedbacks and suggestions to come up with the proper proposal. *Goal:* Improve the llvm-test testsuite. *Idea:* Extend the llvm-test testsuite to include new programs and benchmarks[2]. Test programs should be more CPU intensive

Hi, > 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: the llvm testsuite (from svn, right?) uses

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

*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

Does 'make check' allow just running on a particualar directory of tests ? Many thanks in advance, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090617/e0dc48e4/attachment.html>

On Mar 28, 2009, at 2:17 PM, John Mosby wrote: > 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. > Please! :-) Maybe the wiki too. -bw > llvm/projects/Makefile

Hi, Except for the guide in http://llvm.org/docs/Projects.html#help, is there any easier way to get the llvm projects for famous benchmark suits, such as MiBench, SPEC2000, .etc? In other words, is there preconfigured and downloadable llvm projects for famous benchmark suits? -- Best regards, Li Qingan -------------- next part -------------- An HTML attachment was scrubbed... URL:

From http://www.llvm.org/docs/TestingGuide.html#quickdejagnu : To run only a subdirectory of tests in llvm/test using DejaGNU (ie. Transforms), just set the TESTSUITE variable to the path of the subdirectory (relative to llvm/test): % gmake TESTSUITE=Transforms check On 17-Jun-09, at 1:33 PM, Aaron Gray wrote: > Does 'make check' allow just running on a particualar directory of

I have built and configured the test suits as told at http://llvm.org/docs/TestingGuide.html#testsuite. The llvm is built with configuration: SRC_DIR/configure --prefix=INS_DIR --enable-debug-runtime --disable-optimized --enable-debug-symbols --enable-assertions This configuration is used again in the re-configure process. However, after the re-configure process, the following "make"

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

From http://llvm.org/docs/TestingGuide.html Some tests are known to fail. Some are bugs that we have not fixed yet; others are features that we haven't added yet (or may never add). In DejaGNU, the result for such tests will be XFAIL (eXpected FAILure). In this way, you can tell the difference between an expected and unexpected failure. The tests in the test suite have no such feature at

I am trying to disassemble some bytecode using llvm-dis: llvm-dis -f -o llvmtest/sliceme2.cbc.ll llvmtest/sliceme2.cbc However, I am getting the following error. llvm-dis: Invalid bytecode signature: 464C457F (Vers=0, Pos=4) How do I go about figuring out what the problem is? llvmtest/sliceme2.cbc is newly compiled using the same version of llvm-gcc as llvm-dis. -- Ryan M. Lefever

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

We were successful in upgrading our JIT project to LLVM 3.0rc4 last week, after initially struggling with the various usage and IR changes from V2.9. But we have some follow-up questions: 1) In spite of building and running our tests cleanly with DEBUG+ASSERTS and RELEASE builds, we consistently see a crash when we use a DEBUG build without ASSERTs. The crash appears whenever we use the