search for: fsyntax

Hello all, I am writing test cases which are dedicated to be executed by llvm-lit. Most of my test cases have the same logic but different types. For example: // RUN: %clang_cc1 -fsyntax-only func (int a) { a = 3; } // RUN: %clang_cc1 -fsyntax-only func (char a) { a = 3; } // RUN: %clang_cc1 -fsyntax-only func (unsigned a) { a = 3; } Now I put them in three different test cases but it is hard to maintain. I am wondering whether llvm-lit support writing test cases with macr...

...|.f %{!ffree-form:-ffixed-form} %(cc1_options) \ + %<Wformat %<Wformat-security %<Wno-format-extra-args %<Wno-format- zero-length %<Wno-nonull \ + %{J*} %{I*}\ "/* LLVM LOCAL */" \ %(llvm_options) \ -fpreprocessed %{!nostdinc:-I finclude%s} %{!fsyntax-only:% (invoke_as)}}}}", 0, 0, 0}, @@ -25,21 +27,27 @@ "cc1 -E -lang-fortran -traditional-cpp -D_LANGUAGE_FORTRAN % (cpp_options) \ %{E|M|MM:%(cpp_debug_options)}\ %{!M:%{!MM:%{!E: -o %|.f95 |\n\ - f951 %|.f95 %{!ffixed-form:-ffree-form} %(cc1_options) %{J*} %{I*}...

...nslation phases are vary between compilers. Here's one quick example of how compilers interpret this code differently: |*$* printf '//\\ \nint x=0;\nint x=0;' > f.c||| |||| |||*$* cat f.c||| |||//\ ||| |||int x=0;||| |||int x=0;||| |||| |||*$* clang -fsyntax-only f.c||| |||| |||*$* gcc-4.9 -fsyntax-only f.c||| |||| |||*$* cl f.c||| |||Microsoft (R) C/C++ Optimizing Compiler Version 18.00.21005.1 for x64||| |||Copyright (C) Microsoft Corporation. All rights reserved.||| |||| ||*|f.c(3) : |**|error C2374|**|: 'x...

...ically, it's for asking questions about what's currently tested.. e.g. /Find me all tests for c++11 exceptions/: |git grep 'RUN:.*c++11' -- test/ | grep exceptions| .. experimenting with new features or refactoring existing tests.. e.g. /How many tests could we add -fsyntax-only to?/ |giteach perl -pi -e 's/((RUN:.*%clang_cc1)(.*))$/$2 -fsyntax-only$3/g unless m/(-fsyntax-only|-analyze|-arcmt-check|-arcmt-migrate|-o|-emit-llvm|-E|-ast-print|-ast-dump|[|>]|\\$)/'| Answer, 405. Then git diff and page through to see if any are actionable....

...gle 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. I'll leave it up to others to consider and/or integrate it and consider if /dev/null is portable enough. FLAGS := $(shell gcc -Wall -fsyntax-only -xc /dev/null 2>/dev/null && echo -Wall) CFLAGS := $(shell gcc -Wallme -fsyntax-only -xc /dev/null 2>/dev/null && echo -Wallme) all: @echo flags are $(FLAGS) @echo flags are $(CFLAGS) The down side, these execute every time the fragment is read. If limited to ju...

Google Test requires these CPP FLAGS "-Wno-missing-field-initializers - Wno-variadic-macros" in order to not output warnings. However, these flags are only available with gcc 4.X. We don't want to prevent users from being able to build with gcc 3.X which is the current situation (http://llvm.org/PR3487 ). I've disabled building Google Test in the 2.5 branch. Hopefully

...t; I think that I need to do the following from the website: If you intend to work on Clang C++ support, you may need to tell it how to find your C++ standard library headers. If Clang cannot find your system libstdc++ headers, please follow these instructions: - 'gcc -v -x c++ /dev/null -fsyntax-only' to get the path. - Look for the comment "FIXME: temporary hack: hard-coded paths" in clang/lib/Frontend/InitHeaderSearch.cpp and change the lines below to include that path. After I run 'gcc -v -x c++ /dev/null -fsyntax-only' at the terminal, the follo...

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++/ > ObjC/ObjC++ but not for Fortran > f951: warning: command line option

...g questions about what's currently tested.. > > e.g. *Find me all tests for c++11 exceptions*: > > git grep 'RUN:.*c++11' -- test/ | grep exceptions > > > .. experimenting with new features or refactoring existing tests.. > > e.g. *How many tests could we add -fsyntax-only to?* > > giteach perl -pi -e 's/((RUN:.*%clang_cc1)(.*))$/$2 -fsyntax-only$3/g > unless > m/(-fsyntax-only|-analyze|-arcmt-check|-arcmt-migrate|-o|-emit-llvm|-E|-ast-print|-ast-dump|[|>]|\\$)/' > > Answer, 405. Then git diff and page through to see if any are actio...

...h to the SDK: > > clang++ -isysroot `xcrun --show-sdk-path` > > > Otherwise I always end-up having other issues with missing system/platform > headers. > This gives an error for me. Any ideas? ``` Sean:~/pg/llvm % ~/pg/release/bin/clang++ -v -isysroot `xcrun --show-sdk-path` -fsyntax-only test.cpp clang version 3.9.0 (trunk 274185) (llvm/trunk 274183) Target: x86_64-apple-darwin14.5.0 Thread model: posix InstalledDir: /Users/Sean/pg/release/bin "/Users/Sean/pg/release/bin/clang-3.9" -cc1 -triple x86_64-apple-macosx10.11.0 -Wdeprecated-objc-isa-usage -Werror=deprecate...

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 -fsyntax-only loop1d.c | llvm-dis -o ast.txt* *llvm-dis: Invali...

> 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 don't have one available to play with, so I don't know if it makes any difference. - Chuck

...ng whether clang++ accepts -g... yes checking how to run the C preprocessor... clang -E checking whether clang works... no configure: error: Selected compiler could not find or parse C++ standard library headers. Rerun with CC=c-compiler CXX=c++-compiler ./configure ... When I run 'clang -v -fsyntax-only -x c++ /dev/null' I get: "clang version 2.8 (branches/release_28) Target: x86_64-redhat-linux-gnu Thread model: posix "/usr/bin/clang" -cc1 -triple x86_64-redhat-linux-gnu -fsyntax-only -disable-free -disable-llvm-verifier -main-file-name null -mrelocation-model static...

...jobs.... > gmake[1]: Leaving directory `/home/mgeldiener/dev/clang/build/lib/Support' > gmake: *** [all] Error 1 > > If I build with gcc, there are no problems. I think that we have a new entry for our 'unsupported compilers' list. Please show the output of 'clang -v -fsyntax-only -x c++ /dev/null'. It looks like Mageia 2 has C++ headers in a directory unknown to clang. (So basically, clang from the repository is broken...) Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gr...

...le-checker, and I'd like to detect all the typedefs to recommend switching to using. I'm using libclang 3.8, with the python bindings provided with it. When I parse a file with index = clang.cindex.Index.create() tu = index.parse(f, ['-x', 'c++', '-std=c++11', '-fsyntax-only', '-I', '.']) and then I display the node kinds of every node in the AST (recursively calling get_children() on every node), I get a node of type CursorKind.TYPEDEF_DECL, but only if it is top-level (or inside a namespace or class). If the typedef is in a function body, i...

...yes > checking how to run the C preprocessor... clang -E > > checking whether clang works... no > configure: error: Selected compiler could not find or parse C++ standard > library headers. Rerun with CC=c-compiler CXX=c++-compiler ./configure ... > > When I run 'clang -v -fsyntax-only -x c++ /dev/null' I get: > > "clang version 2.8 (branches/release_28) > Target: x86_64-redhat-linux-gnu > Thread model: posix > "/usr/bin/clang" -cc1 -triple x86_64-redhat-linux-gnu -fsyntax-only > -disable-free -disable-llvm-verifier -main-file-name null...

...ode generation (I think the > timeframe of a GSoC project and the complexity of C++ doesn't allow full > C++ support to be developed). Ok, remember that parsing is only one piece of the puzzle. We also have semantic analysis/typechecking/ASTBuilding as well. I think that focusing on -fsyntax-only is a good place to be. > C++ parsing support includes (but is not limited to): > -Namespace declarations, using directives. > -Class declarations, class members, methods etc. > -Overload method/function matching. > -C++ name lookup rules, scope resolution. > -Class/function...

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

...9;. If you're not on a Mac, you'll need to make one change: paths to system header files are currently hard coded into the tool. To get this to work for you, you'll probably have to change clang/Driver/clang.cpp:606 to include the paths that 'touch empty.c; gcc -v empty.c -fsyntax-only' prints (it should list some lines after "#include <...> search starts here:"). Once this is built, you can compile C code (amazing, I know!). The clang driver takes a lot of GCC compatible options, which you can see with 'clang --help'. As a simple exampl...

Chris and Bill, I have tested the proposed patch from... http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-August/016490.html under i686-apple-darwin9 and it solves the problems building gfortran from llvm svn. The resulting compiler works fine so can we get that patch in before 2.4 is release? Jack ps We do have one oddity left in llvm-gfortran from current llvm svn. I find