similar to: [LLVMdev] Does llvm-lit support type substitution (macro)?

On 08/12/2013 16:43, Daniel Dunbar wrote: > > With one-to-one mapping, it becomes possible to use simple tools > like grep to validate common mistakes like %clang / %clang_cc1 > mixups, a missing -o flag and so on. > > Right now there's no obvious way to do those checks and we've > ended up without an easy way to lint for broken tests as a result.

Ok, that makes sense. I don't see this as a good enough argument to remove backslash support though. For problems like the clang_cc1 substitution mistakes, it would be much better to just improve the substitution support so that those cause immediate test failures. I would definitely support a move to make lit's substitution machinery more strict. For problems like your first search, I

On Sun, Dec 8, 2013 at 6:04 AM, Alp Toker <alp at nuanti.com> wrote: > > On 08/12/2013 13:12, Chandler Carruth wrote: > >> >> * Removing trailing \ will introduce the neat property that >>> >>> one RUN line corresponds precisely to one command that's >>> executed. This is good for humans and will enable

On 08/12/2013 13:12, Chandler Carruth wrote: > >> * Removing trailing \ will introduce the neat property that >> one RUN line corresponds precisely to one command that's >> executed. This is good for humans and will enable >> simplifications in the test runner. >> >> FWIW, I've never really had a

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 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 10/12/2013 19:47, Jim Grosbach wrote: > > On Dec 10, 2013, at 11:26 AM, Alp Toker <alp at nuanti.com > <mailto: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

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Alp Toker > Subject: Re: [LLVMdev] lit: deprecating trailing \ in RUN lines > //\ > int x=0; > int x=0; > $ gcc-4.9 -fsyntax-only f.c Try gcc with -Wall, and you'll see the appropriate warning. Also try the MS compiler after removing the trailing space after the backslash; I

On Dec 10, 2013, at 1:43 PM, Caldarale, Charles R <Chuck.Caldarale at unisys.com> wrote: >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] >> On Behalf Of Alp Toker >> Subject: Re: [LLVMdev] lit: deprecating trailing \ in RUN lines > >> //\ >> int x=0; >> int x=0; > >> $ gcc-4.9 -fsyntax-only f.c > > Try

Following came from tools/clang/test/CodeGenObjC/message-arrays.m. But I don't know how to compile it at terminal command since no clang_cc1 executable file. Can some one help me? I am writing the llvm backend document --http://jonathan2251.github.com/lbd/index.html now. I use "clang -c hello.cpp -emit-llvm" to compile C++ but don't know how to compile Object-C. // RUN:

As long as the individual commands are still copy-pastable into both cmd and bash, I'm happy. I think practice this means the output should look more like this: some test: // RUN: %clang_cc1 %s -verify output: $ "C:\\src\\llvm\\build\\bin\\clang.exe" -cc1 "C:\\....\\test.cpp" -verify Essentially every program used in the LLVM test suite understands forward slashes, so we

On Oct 30, 2008, at 11:02 PM, Chris Lattner wrote: > On Oct 30, 2008, at 5:23 PM, Jack Howarth wrote: >> ps We do have one oddity left in llvm-gfortran from current llvm >> svn. I find everytime I compile something with llvm-gfortran that >> I get a series of warning messages... >> >> f951: warning: command line option "-Wformat" is valid for C/C++/

Look up --emit-llvm. I think it has to be used with -c. On Apr 5, 2013 10:55 PM, "Jonathan" <gamma_chen at yahoo.com.tw> wrote: > Following came from tools/clang/test/CodeGenObjC/message-arrays.m. But I > don't know how to compile it at terminal command since no clang_cc1 > executable file. Can some one help me? I am writing the llvm backend > document

I got the following compile error. Did the message-arrays.m can be compiled into .bc? Or need include something for Object C language compile. Jonathan 118-165-76-229:CodeGenObjC Jonathan$ pwd /Users/Jonathan/llvm/release/src/tools/clang/test/CodeGenObjC 118-165-76-229:CodeGenObjC Jonathan$ clang -emit-llvm -o 1.ll -c message-arrays.m message-arrays.m:5:3: warning: instance method

We currently don't use pipefail when running test under make check. This has the undesirable property that it is really easy for tests to bitrot. For example, something like llc %s | FileCheck %s will still pass if llc crashes after printing what FileCheck was looking for. It is also easy to break the tests when refactoring. I have fixed tests that were doing %clang_cc1 -a-driver-options

On Apr 5, 2013, at 9:19 PM, Jonathan wrote: > I got the following compile error. Did the message-arrays.m can be compiled into .bc? Or need include something for Object C language compile. Those are warnings, not errors. They otherwise compiled just fine. You should have a bitcode file named '1.ll' from each of those commands. Chip > > Jonathan > >

On Feb 4, 2009, at 9:10 PM, Tanya Lattner wrote: > Ideally, configure should detect what version of gcc you have and > either use those CPP FLAGS or not (it will output warnings with > 3.X). Or, we just disable building Google Test by default. > Can anyone help with this? Here is a Makefile fragment that will dynamically test gcc and add flags, if the flag is supported.

On Wed, Jul 6, 2016 at 1:21 PM, Mehdi Amini via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On Jun 23, 2016, at 11:15 AM, Cristianno Martins via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hi Vivek, > > you can also include these lines below to your ~/.bash_profile: > > LLVM_BUILD="/Developer/llvm/build" # Path to your build directory

Hi Renato, Thanks for the help. I am trying to follow the AST way. I tried seeing the AST contents by using following command: *clang -Xclang -ast-dump -fsyntax-only loop.c* This is giving me some AST output( I believe so) but I am having two issue: 1. I am not able to put this output in a file as Its showing following error: *yaduveer at yaduveer-Inspiron-3542:~/RP$ clang -Xclang -ast-dump

On 01/09/2013 10:37 AM, Dmitri Gribenko wrote: > On Tue, Jan 8, 2013 at 8:43 AM, Edward Diener > <eldlistmailingz at tropicsoft.com> wrote: >> After applying your patch on Mageia 2 and invoking llvm's configure: >> >> Using clang 3.0 I get: >> >> "checking whether clang works... no >> configure: error: Selected compiler could not find or