similar to: [LLVMdev] Blocks/Closures + Clang + LLVM

So, when performing expression evaluation, lldb trips over an assert in clang/lib/AST/RecordLayoutBuilder because ExternalFieldOffsets doesn't contain a FieldDecl that updateExternalFieldOffset expected. I found that the assert occurs when both static and non-static member variables are present. For instance, with the following, the lldb command 'expr my_test.length()' does not

FYI, this turned out to be an error of omission in LLDB in SymbolFileDWARF, because the case of a non-defining external (i.e. a static member variable) wasn't being handled with a variable lookup to dig up the location. I'll put a patch together for lldb-commits, - Ashok From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Thirumurthi, Ashok

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

llvm[1]: Compiling APFloat.cpp for Release+Asserts build clang: TargetInfo.cpp:1778: llvm::Type *GetX86_64ByValArgumentPair(llvm::Type *, llvm::Type *, const llvm::TargetData &): Assertion `Lo->isIntegerTy() && "Invalid/unknown lo type"' failed. 0 clang 0x0000000001c132ef 1 clang 0x0000000001c13804 2 libpthread.so.0 0x00002ba7d7eaec60 3

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++/

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

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.

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.

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 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

Hello Pedro, As others have said we're assuming that you're using Clang as the frontend, the MSP430TargetInfo class inside lib/Basic/Targets.cpp (clang codebase) set ints to be 16 bits wide, so you should get 16bit mults straight away without promotion. But anyways for 8bit multiplicantions you can do the following to bypass argument promotion: 1) go to the lib/CodeGen/TargetInfo.cpp

> 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 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

Hello, I'm trying to use the python libclang bindings to write a C++ style-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',

On Mon, Jan 7, 2013 at 12:23 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > On Mageia 2 I have installed the binary clang package clang3.0-7. When I > tried to build the latest llvm/clang from source using this binary clang > I get this error: > > 1) In file included from > /home/mgeldiener/vcs/llvm/lib/Support/Signals.cpp:30: >

Dear All, I’m working on a project that extends C. I’m adding a new type of pointer that is a fat pointer. It has some metadata about the pointed object besides the starting address of the object. Currently I implemented this pointer as an llvm:StructType. In llvm::Type generation function llvm::Type *CodeGenTypes::ConvertType(QualType T) in the case for clang::Type::Pointer, instead of creating

On Sun, Jan 13, 2013 at 12:59 AM, Edward Diener <eldlistmailingz at tropicsoft.com> wrote: > 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: >>> >>>

> 1. Clang - Jay, do you have a patch for this? Yes. It's good enough to build most of LLVM+Clang, except for a couple of files. But I'm running out of time and expertise to be able to fix the remaining bits. Some specific concerns: 1. Many Objective-C(++) tests fail, because they use implicitly defined structs for various ObjC runtime data structures; the ASTConsumer

On Wed, 19 Mar 2008, Argiris Kirtzidis wrote: > I'd like to hear your opinions and ideas for a proposal to improve > support for C++ parsing for LLVM's clang front end. Some meta feedback: C++ support in clang is a huge project, far and away more than any mortal can get done in a summer. While it would be possible to sketch out the parser itself in the summer (providing the