similar to: [LLVMdev] testing with llvm-lit

when I execute clang on llvm bitcode files, I get the following error: clang: error: unable to execute command: Aborted unsupported GC: vmkit UNREACHABLE executed at GCMetadata.cpp:87! 0 clang 0x09e9d5d9 llvm::sys::PrintStackTrace(_IO_FILE*) + 41 Stack dump: 0. Program arguments: /home/ali/llvm-3.3.src/Release+Asserts/bin/clang -cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all

Hi, Since I want to write tests with llvm-lit, I pulled the latest revision of LLVM from SVN HEAD and tried to run the following command (copied from http://llvm.org/docs/TestingGuide.html): $ ~/llvm/Debug+Asserts/bin/llvm-lit ~/llvm/test/Integer/BitCast.ll llvm-lit: lit.cfg:103: fatal: No site specific configuration available! Any ideas on why this happens? Thanks, Brice

2010/11/8 Brice Lin <brice.lin at gmail.com>: > $ ~/llvm/Debug+Asserts/bin/llvm-lit ~/llvm/test/Integer/BitCast.ll > llvm-lit: lit.cfg:103: fatal: No site specific configuration available! Have you ever run "make check" and passed? ...Takumi

Hi, I am not sure if this is the right forum. Please direct me to the appropriate place if it isn't so. Please keep in CC as i am not subscribed to this mailing list. I am trying to test riscv llvm tools in QEMU using llvm testsuite. As a trial i am trying only the Single Source C Regression folder. The steps that i took are : ]$ cmake -DCMAKE_C_COMPILER=/opt/riscv-tools/bin/clang

I'm developing an llvm-based compiler and when I try to generate executable file the following error occurs: ./bin/llvmcode.s:35: undefined reference to `operator new[](unsigned long)' Note that in the generated IR, the function '@_Znam' is called which is located in one of llvm libraries. So, I should have linked the generated assembly file with that library. Here is the code I

So I started prototyping remote testing for libcxx over the weekend: https://github.com/jroelofs/libcxx/tree/remote_test The SSHExecutor isn't quite finished yet, but this should give an idea of what I've got in mind. Does this look generic enough to work for other projects under the llvm-umbrella (LNT, test-suite, compiler_rt, libcxxabi, etc)? Are there use cases that you see

Morning, Will! 2012/7/12 Will Schmidt <will_schmidt at vnet.ibm.com>: > llvm]$ gmake check > llvm[0]: Running test suite > gmake[1]: Entering directory `/home/willschm/llvm/test' > Making LLVM 'lit.site.cfg' file... > sed: file lit.tmp line 8: unknown option to `s' > gmake[1]: *** [lit.site.cfg] Error 1 > > The relevant lines in test/Makefile: >

Hi, Using trunk llvm ; on powerpc (powerpc64/power7); trying to do a "gmake check", the sed bits in test/Makefile appear to be getting tripped up when trying to generate lit.site.cfg. I've started to hack at it, made a little bit of progress, but wonder if I'm just digging myself a hole. Highlights of what I've poked at are below.. Comments or thoughts? Thanks,

On Wed, Jan 9, 2013 at 5:32 AM, Ali Sedaghat <ali.sedaghatbaf at gmail.com> wrote: > I'm developing an llvm-based compiler and when I try to generate > executable file the following error occurs: > > ./bin/llvmcode.s:35: undefined reference to `operator new[](unsigned > long)' > > Note that in the generated IR, the function '@_Znam' is called which is

Hi everyone, I am sending this email after some time consuming exploration into how LLVM executes its tests. I first noticed this issue when Rafael noticed that my patch I sent in to llvm-commits broke some tests. I was initially very skeptical, as I had run the make check test from the build directory before sending in the patch, but as it turns out, several issues came together in a perfect

2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > I just created clang with the tarballs without problem; however, > when `make check-all` was run, I got 1 error. My system is: > ~/download/llvm/pre-releases/3.2/rc3/download/build_debug $ make check-all > llvm[0]: Running test suite > make[1]: Entering directory >

Hello, LLVM community. I've built a cross-toolchain on Windows and I'm now trying to run unit tests for the LLVM libraries. I used Ninja as a build system and MSVC as host compiler without an issue, but when I try to run 'ninja check-llvm-unit', I get the following error: llvm-lit.py: C:/Users/sergej/Developer/llvm-project/llvm\utils\lit\lit\TestingConfig.py:102: fatal: unable

Hi, I'm new to llvm and am trying to run benchmarks from the test-suite using lnt to check loop-vectorization for various benchmarks. Test are compiling and executing fine, but I am not getting optimization remarks while using flags like -Rpass-missed=loop-vectorize and -Rpass-analysis=loop-vectorize I've tried running it like this: lnt runtest test-suite --sandbox SANDBOX --cc

On Sun, Dec 30, 2012 at 1:58 AM, Larry Evans <cppljevans at suddenlink.net>wrote: > On 12/29/12 18:40, NAKAMURA Takumi wrote: > > 2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > >> I just created clang with the tarballs without problem; however, > >> when `make check-all` was run, I got 1 error. My system is: > > > >>

On Dec 8, 2013, at 4:24 AM, Alp Toker <alp at nuanti.com> wrote: > > On 08/12/2013 11:22, Chandler Carruth wrote: >> On Sun, Dec 8, 2013 at 2:11 AM, Alp Toker <alp at nuanti.com> wrote: >> I'd like to propose deprecating and shortly thereafter removing the lit test runner feature that concatenates RUN lines ending in a trailing \ >> >> I'm

On 9/8/14, 3:31 PM, Greg Fitzgerald wrote: > Jon, > >> One issue to start with is that none of the libcxx/libcxxabi tests have RUN lines. > > Sorry, I didn't mean to imply that 'RUN:' lines should be added to > libcxx tests. It's fine that every one is implicitly: > > // RUN: %clang %s -o %t && %run %t > ... and then when an explicit

On Dec 10, 2013, at 11:26 AM, Alp Toker <alp at nuanti.com> wrote: > > On 10/12/2013 18:03, Jim Grosbach wrote: >>> That causes dissonance between what the compiler sees and what lit.py sees for no particularly good reason. One of the nice properties of lit tests is that they're also valid compiler inputs, so trailing slash is a bit unfortunate. >>> >>

On 12/06/12 01:12, Pawel Wodnicki wrote: > Hello, > > Release Candidate 3 has been branched. > RC3 source code can be downloaded as tarballs from: > > http://llvm.org/pre-releases/3.2/rc3/ > > or directly from svn. > > Binaries will be posted shortly. > > Testing > > RC3 has a number of fixes related to MIPS support > that need to be well

Dan/Daniel/Eric, I'm testing a bare-metal ARM toolchain, and I've hacked up my local copy of lit to get it to run libcxx tests on qemu. I wanted to pick your collective brains to see if there was a better way of doing this. What I have implemented is here (don't take this as a formal review request, we can do that later once we figure out the best direction to go): lit part:

Dear all, Recently I've considering using LIT for my benchmark testing framework, and the only reference for LLVM-LIT is the man page and some READMEs. I don't find any documentations on config, which seems to be quite important to the tool. If I use lit outside LLVM source tree and use on my own test files, LIT marks them as 'unresolved'. So are there any documentations I can