similar to: [LLVMdev] HOWTO use llvm lit tool

> On Dec 6, 2017, at 10:21 AM, Zachary Turner <zturner at google.com> wrote: > > Can I have some assurance that if it fails again, someone will look into who has access to the builders so I don't have to keep doing speculative commits? Sure. I did this last time and I promise to also do it this time. -- adrian > > On Wed, Dec 6, 2017 at 10:13 AM Adrian Prantl

So I manage to get clang's colored output through ninja simply by force (CMAKE_CXX_FLAGS=-fcolor-diagnostics), which isn't ideal (if I were to pipe ninja's output to a file it'd still have color escapes, etc) but it works. But I haven't found a similar solution for FileCheck & I'm wondering has anyone already solved this problem for themselves - if so, how? if not,

Hi Zachary: I was able to reproduce the greendragon results locally (OSX), and fix the problem by excluding 'debuginfo-tests' from check-clang -- this prevents them from being added twice, once for check-clang and again for check-debuginfo. Below are the minimized patches I used to reproduce and fix the problem -- based on your originals. I've verified these patches work when

> On Dec 6, 2017, at 10:10 AM, Zachary Turner <zturner at google.com> wrote: > > Adrian, Mike, Chris? Any update on this? I've temporarily switched to working on something different, but I plan to be back on this in a couple of weeks. It's been a month since my first revert of this CL, which seems like a reasonable amount of lead-time to deal with issues surrounding

I just want to update test/Transforms/LowerSwitch/feature.ll that already uses grep. It uses grep + count, probably due to shorter construction. -Stepan. Eric Christopher wrote: > > On May 24, 2012, at 12:12 AM, Stepan Dyatkovskiy wrote: > >> Hi all. I found that if you want to use grep with escape characters in >> lit, you should pass it within the double slash (\\). Since

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 "ninja" for example, or "ninja check-llvm", it's automatically

On 2019-01-24 20:17, David Greene via llvm-dev wrote: > alexp via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> I have a project which uses llvm, but is (at least not yet) a >> contribution / not in the source tree of llvm. >> Is it a good idea (e.g. instead of using boost test framework) to use >> the llvm testsuite related tools in this case? > >

Is there a way to do this with llvm-lit, i.e., use the equivalent of backticks? foo takes a single argument, but doesn't read from stdin. // RUN foo some_arg > %t; FileCheck %s < %t // RUN foo `cat %t` | FileCheck --check-prefix=INVERSE // CHECK: {{^[0-9]+$}} // INVERSE: some_arg thanks... don -------------- next part -------------- An HTML attachment was scrubbed... URL:

How can I platform-conditionally compile/check sections of code with lit? Can I rely on preprocessor defines like _WIN32? Specifically, I'm adding new tests to existing lit tests, but the new tests should only be compiled and run on Windows. Sincerely, Alexander Riccio -- "Change the world or go home." about.me/ariccio <http://about.me/ariccio> If left to my own devices, I

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

Hi Evan, Thanks for your time. You're adding a feature that embed code inside a module. When the module is > loaded, is the string going to be verified? How are users of LLVM IR able > to ensure the embedded string is safe? I am not saying it cannot be done. > This feature just increases the risk and that again raises the bar for > acceptance. > I think the embedded string in

Hi, I am observing a deadlock with llvm-lit on windows 7. When I attached a debugger, the communicate() call is blocked. In file utils/lit/lit/TestRunner.py > # FIXME: There is probably still deadlock potential here. Yawn. > procData = [None] * len(procs) > procData[-1] = procs[-1].communicate() I am invoking python directly on windows to run the unit tests.

On Thu, May 24, 2012 at 12:44 AM, Stepan Dyatkovskiy <stpworld at narod.ru>wrote: > I just want to update test/Transforms/LowerSwitch/feature.ll that > already uses grep. > It uses grep + count, probably due to shorter construction. > If you are touching such a test, please convert it to FileCheck. Use of 'grep' in tests is an endless source of problems, and we are

Hi all. I found that if you want to use grep with escape characters in lit, you should pass it within the double slash (\\). Since the first one is captured by python scripts and the second one by grep. E.g. if you want to capture "grep icmp ule" you should pass "grep icmp\\ ule" So I'm going to commit the test with strings like this. How stable this feature in lit?

Hi all, quite a few tests use the pattern "2>&1 | FileCheck %s". AFAIK how stdout and stderr are merged into a single character stream is undefined and depends e.g. on whether stdout is buffered. I think we are often saved by the fact that standard output is written only at the end of the program and stderr is unbuffered, i.e. always written before stdout. A lot of tests disable

I'm trying to put together some tests for the optimization bisecting feature I'm working on and I've come across a stumbling block trying to accomplish something in a lit test. I've got an IR file with some simple functions, one of which includes a call to another function that will be inlined during optimization. I can use this to manually test my new OptBisect class by invoking

Hi, I was wondering if there is a way with llvm-lit and FileCheck to identify if a specific test should run or not based on the processor architecture. For example, I have a test that can run only in an Intel KNL, so if I run the tests in a Sandybridge I want to ignore that test. Any idea? Thanks! Simone ----------------------------------------------------------------------------------- This

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. >> > > How does the backslash break this in any way? The backslash is

On May 24, 2012, at 12:12 AM, Stepan Dyatkovskiy wrote: > Hi all. I found that if you want to use grep with escape characters in > lit, you should pass it within the double slash (\\). Since the first > one is captured by python scripts and the second one by grep. > E.g. if you want to capture "grep icmp ule" you should pass > "grep icmp\\ ule" > > So

Hi, I have a project which uses llvm, but is (at least not yet) a contribution / not in the source tree of llvm. Is it a good idea (e.g. instead of using boost test framework) to use the llvm testsuite related tools in this case? Alex