search for: nameddecl

...ith modules. Adding them was intentional :-) > > To clarify, this is not so much about the appearance of new builtins > but that the structure has fields with no name. Other builtin > structures like __va_list_tag have names on their fields. FieldDecl > derives (indirectly) from NamedDecl. > > Our concern is that AST processing tools expect to find a name on > fields, and the changes in question introduced fields without names. > Can they be given names, if only for AST consistency? Yes, sounds like a good idea. I’ll take a look at this later today. > > Thanks,...

...) llvm[4]: Compiling Indexing.cpp for Release+Asserts build (PIC) llvm[4]: Compiling IndexingContext.cpp for Release+Asserts build (PIC) /home/ecsardu/LLVM/llvm/tools/clang/tools/libclang/IndexingContext.cpp: In member function 'void clang::cxindex::IndexingContext::handleReference(const clang::NamedDecl*, clang::SourceLocation, const clang::NamedDecl*, const clang::DeclContext*, const clang::Expr*, CXIdxEntityRefKind)': /home/ecsardu/LLVM/llvm/tools/clang/tools/libclang/IndexingContext.cpp:401:68: warning: cast from type 'const clang::Decl*' to type 'clang::Decl*' casts away qu...

Hi all， Clang use a hash table to store all its identifiers. The hash table definition is: typedef llvm::StringMap<IdentifierInfo*, llvm::BumpPtrAllocator> HashTableTy; HashTableTy HashTable; Can anyone explain the mechnism of handling the name string key collision for me? Is there a IdentifierInfo objects chain or list for variable or function with the same name? Thanks very much!

...SConstantString_tag are now exposed. >> To clarify, this is not so much about the appearance of new builtins >> but that the structure has fields with no name. Other builtin >> structures like __va_list_tag have names on their fields. FieldDecl >> derives (indirectly) from NamedDecl. >> >> Our concern is that AST processing tools expect to find a name on >> fields, and the changes in question introduced fields without names. >> Can they be given names, if only for AST consistency? > > Yes, sounds like a good idea. I’ll take a look at this later t...

Hi I am the maintainer of pygccxml, which uses clang/llvm and CastXML to parse c++ code. A user reported a problem with the current llvm 3.9 trunk version (I tested with r261262). Our problem is that the AST contains some declarations which were not there before. Using "clang -Xclang -ast-dump” on a c++ file, I get the following result: TranslationUnitDecl 0x8e41ab0 <<invalid

Hi, I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. Cheers, James ________________________________________ From: Csaba Raduly [rcsaba at gmail.com] Sent: 23 October 2011 18:44 To: James Molloy Cc: Paul Berube; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] build warnings On Sat, Oct 22,

On Sat, Oct 22, 2011 at 12:24 AM, James Molloy wrote: > Hi Paul, > > That should be easy enough, because the LLVM build has no warnings in it! > > Some of us build with -Werror, and even with those of us that don't warnings are not tolerated. You're already seeing all the warnings that are coming out of the build :) So, all the "variable might be used

...ypedValueRegion*)’: /home/greened/src/llvm-30-rc3/clang-3.0rc3.src/lib/StaticAnalyzer/Core/RegionStore.cpp:1280:12: warning: variable ‘T’ set but not used [-Wunused-but-set-variable] /home/greened/src/llvm-30-rc3/clang-3.0rc3.src/lib/Sema/SemaTemplateInstantiateDecl.cpp: In member function ‘clang::NamedDecl* clang::Sema::FindInstantiatedDecl(clang::SourceLocation, clang::NamedDecl*, const clang::MultiLevelTemplateArgumentList&)’: /home/greened/src/llvm-30-rc3/clang-3.0rc3.src/lib/Sema/SemaTemplateInstantiateDecl.cpp:3170:12: warning: variable ‘SawNonDependentContext’ set but not used [-Wunused-but...

On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote: > We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: > >        http://llvm.org/pre-releases/3.0/rc3/ > > for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your

...tag are now exposed. >>> To clarify, this is not so much about the appearance of new builtins >>> but that the structure has fields with no name. Other builtin >>> structures like __va_list_tag have names on their fields. FieldDecl >>> derives (indirectly) from NamedDecl. >>> >>> Our concern is that AST processing tools expect to find a name on >>> fields, and the changes in question introduced fields without names. >>> Can they be given names, if only for AST consistency? >> >> Yes, sounds like a good idea. I’ll ta...

Hi All, We have populated info in the Clang Sema i.e class Sema (include/clang/Sema/Sema.h) and like to propagate the same to Clang Codegen . Currently we are propagating through ASTContext ,where we have duplicating fields info and operation in the Sema and ASTContext . Any better way of doing the same ? Thank you ~Umesh

Good day, LLVMers! We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: http://llvm.org/pre-releases/3.0/rc3/ for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your projects, and let us know if you find any regressions from the 2.9 release. Please keep

On Mon, Oct 13, 2014 at 4:14 PM, Chandler Carruth <chandlerc at google.com> wrote: > 1. Initialisms. It's common in Clang code (also in LLVM?) to use >> initialisms as variable names. This doesn't really seem to work for names >> that start with a lower case letter. >> > > I think wee at least need a good answer to this. > As I really suspect this is