search for: lit

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 'unresolv...

As of r313998, this workflow no longer works: cd <build-dir> ./bin/llvm-lit <src>/llvm/tools/clang/test/CoverageMapping I get: llvm-lit: /Users/vk/src/llvm.org-coverage-braces/llvm/tools/clang/test/lit.cfg.py:97: note: using clang: '/Volumes/Builds/llvm.org-coverage-braces-RA/bin/clang' llvm-lit: /Users/vk/src/llvm.org-coverage-braces/llvm/utils/lit/lit/Tes...

This works for me. Can you run "which clang-func-mapping" and also add a line to clang/test/lit.cfg.py to print the value of config.environment['PATH']? On Fri, Sep 22, 2017 at 11:27 AM Zachary Turner <zturner at google.com> wrote: > Looking, thanks for the report. > > On Fri, Sep 22, 2017 at 11:22 AM Vedant Kumar <vsk at apple.com> wrote: > >> As of r3...

...all the tests, then run an individual test. >> >> IIRC like so: >> >> git clone llvm ...... >> cd llvm/tools >> git clone clang ..... >> cd ../../ >> mkdir build >> cd build >> cmake ../llvm >> ninja check-clang >> ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c >> > > Hi Brian, > > The cmake-line should be... > > # apt-get install ninja-build > $ cmake -G Ninja ../llvm > > Unfortunately, on the latest Git my build fails which gcc-7 (see > attached file for details). > Do I really...

llvm-lit is already put into <output-tree>/bin by CMake. There is a CMake target called `llvm-lit` that will generate the <output-dir>/bin/llvm-lit script. If you built only a few specific llvm targets such as FileCheck, etc then you may need to run this lit target manually. If you just run &...

Hi, while experimenting with llvmlinux on Debian/testing AMD64 I wanted to run some x86-64 ASM tests. I fell over [1] and wanted to run it. So, I cloned clang from Git... $ git clone https://github.com/llvm-mirror/clang.git I looked through some docs where I have seen I need "llvm-lit" or "lit.py". The Debian package llvm-7-tools from <apt.llvm.org> does ship "lit.py". Furthermore, I have installed llvm-7 and clang-7 packages. The version is 1:7~svn330207-1~exp1+0~20180417201234.1709~1.gbp6fb10d. [5,6] have some examples on running a single testca...

...f is to clone both > llvm and clang repos, run all the tests, then run an individual test. > > IIRC like so: > > git clone llvm ...... > cd llvm/tools > git clone clang ..... > cd ../../ > mkdir build > cd build > cmake ../llvm > ninja check-clang > ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c > Hi Brian, The cmake-line should be... # apt-get install ninja-build $ cmake -G Ninja ../llvm Unfortunately, on the latest Git my build fails which gcc-7 (see attached file for details). Do I really need to build clang-from-git? I have llvm-7/clang-7 binarie...

Hi, A feature I've wanted in lit for a while is a having a timeout per test. Attached are patches that implement this idea. I'm e-mailing llvm-dev rather than llvm-commits because I want to gather more feedback on my initial implementation and hopefully some answers to some unresolved issues with my implementation. Currently...

> On Sep 22, 2017, at 11:36 AM, Vedant Kumar <vsk at apple.com> wrote: > > Ah, the problem goes away once I build clang-func-mapping. > > I stripped some stuff out, but here's pretty much what clang/test/lit.cfg.py says my PATH is: > > ** PATH **: /Volumes/Builds/llvm.org-coverage-braces-RA/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin > > I wonder how this ever worked before, when I didn't have clang-func-mapping built. Oh, this might be an issue with r313975, which I picked up...

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 to parse config file 'C:\\Users\\sergej\\Developer\\llvm-project\\llvm\\test\\Unit\\lit.cfg.py', traceback: Traceback (most recent call last): File "C:/Users/sergej/Developer/llvm-projec...

...f is to clone both > llvm and clang repos, run all the tests, then run an individual test. > > IIRC like so: > > git clone llvm ...... > cd llvm/tools > git clone clang ..... > cd ../../ > mkdir build > cd build > cmake ../llvm > ninja check-clang > ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c > > > Hi Brian, > > The cmake-line should be... > > # apt-get install ninja-build > $ cmake -G Ninja ../llvm > > Unfortunately, on the latest Git my build fails which gcc-7 (see > attached file for details). > Do I really need to...

Ah, the problem goes away once I build clang-func-mapping. I stripped some stuff out, but here's pretty much what clang/test/lit.cfg.py says my PATH is: ** PATH **: /Volumes/Builds/llvm.org-coverage-braces-RA/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin I wonder how this ever worked before, when I didn't have clang-func-mapping built. Anyway, thanks for your help! vedant > On Sep 22, 2017, at 11:31 AM, Zach...

Looking, thanks for the report. On Fri, Sep 22, 2017 at 11:22 AM Vedant Kumar <vsk at apple.com> wrote: > As of r313998, this workflow no longer works: > > cd <build-dir> > ./bin/llvm-lit <src>/llvm/tools/clang/test/CoverageMapping > > I get: > > llvm-lit: /Users/vk/src/llvm.org-coverage-braces/llvm/tools/clang/test/ > lit.cfg.py:97: note: using clang: '/Volumes/Builds/llvm.org > -coverage-braces-RA/bin/clang' > llvm-lit: /Users/vk/src/llvm.org-cov...

Hi all, I've got https://reviews.llvm.org/D37756 up for review currently which simplifies a lot of the logic in our lit config files. For most people, this will be completely transparent and "just work", but it breaks one workflow that people should be aware of. Problem: If you run lit by putting llvm-config in your path and then running <source-root>/utils/lit/lit.py <source-root>/<path-t...

The simplest way to run a clang test case that I know of is to clone both llvm and clang repos, run all the tests, then run an individual test. IIRC like so: git clone llvm ...... cd llvm/tools git clone clang ..... cd ../../ mkdir build cd build cmake ../llvm ninja check-clang ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c On Sun, May 6, 2018 at 7:10 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > while experimenting with llvmlinux on Debian/testing AMD64 I wanted to > run some x86-64 ASM tests. > > I fell over [1] and wanted to...

What are all the different ways people run lit? I'm doing some refactoring and want to make sure I have all the based covered. Obviously you can use check-llvm. And you can also run llvm-lit.py in your bin directory and point it to your source tree. What else? Both of the aforementioned methods require running cmake first, is there any...

Yea at first I was worried that maybe I changed the semantics of how it looked in PATH, and you had clang-func-mapping in your PATH somewhere before but now lit was building a different PATH. But I looked at that change and it wasn't even creating that substitution before. So it looks like that CL is indeed the problem. On Fri, Sep 22, 2017 at 11:38 AM Vedant Kumar <vsk at apple.com> wrote: > > > On Sep 22, 2017, at 11:36 AM, Vedant...

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, -Will llvm]$ gmake check llvm[0]: Running test suite gmake[1]: Entering directory `...

...make And I tried to do a nmake check (which works for MinGW and "mingw32-make check") and get the following error: >Scanning dependencies of target check >[100%] Running LLVM regression tests >Traceback (most recent call last): > File "M:/Development/Source/LLVM/utils/lit/lit.py", line 5, in <module> > lit.main() > File "M:\Development\Source\LLVM\utils\lit\lit\main.py", line 515, in main > testSuiteCache, localConfigCache)[1]) > File "M:\Development\Source\LLVM\utils\lit\lit\main.py", line 230, in getTests >...

...2374. Please > file issues against it. > > Thanks for helping with the release! This time I got an error during check-all, on i386-unknown-freebsd10: [...] gmake[1]: Entering directory `/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/test' Making LLVM 'lit.site.cfg' file... Making LLVM unittest 'lit.site.cfg' file... gmake -C /home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-rc2.obj/test/../tools/clang/test lit.site.cfg Unit/lit.site.cfg gmake[2]: Entering directory `/home/dim/llvm-3.6.0/rc2/Phase3/Release/llvmCore-3.6.0-...