search for: translationunitdecl

Been having a bit of a problem with dyn_cast: Suppose I have a class A that inherits from two base classes, both of which support dyn_cast. In order to use dyn_cast on A, I need to do a bunch of extra work: 1) Since dyn_cast uses reinterpret_cast rather than static_cast, the pointer value won't get adjusted by the cast operation, making the pointer invalid. I end up having to redefine

...solve the question: how do I smuggle some metadata on the module level, from the frontend to the generated object file (in an hopefully sane and reusable manner). So, the solution I thought about was the following. The gathered information is but into a NamedMetadataStringAttr and attached to the TranslationUnitDecl. This would be, as far as I can see, the first annotation on the TranslationUnit level. Attributes seem to me the best solution at that point, since there is already a good infrastructure in clang. TranslationUnitDecl | NamedMetadataAttr implicit llvm.extra_section clang.analysis "Infor...

..., and "InclusionDirective". AST will be extended to support two new DECL types: "MacroDecl" and "FileIncludeDecl". Where "FileIncludeDecl" AST might contain other "FileIncludeDecl"/"MacroDecl" ASTs. These two new AST DECLs are not part of TranslationUnitDecl and are handled separately (see AST example below). In the LLVM IR, metadata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIF...

...smuggle some > metadata on the module level, from the frontend to the generated object > file (in an hopefully sane and reusable manner). > > So, the solution I thought about was the following. The gathered > information is but into a NamedMetadataStringAttr and attached to the > TranslationUnitDecl. This would be, as far as I can see, the first > annotation on the TranslationUnit level. Attributes seem to me the best > solution at that point, since there is already a good infrastructure in > clang. > > TranslationUnitDecl > | NamedMetadataAttr implicit llvm.extra_sectio...

...reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) Where "FileIncludeDecl" AST might contain other "FileIncludeDecl"/"MacroDecl" ASTs. These two new AST DECLs are not part of TranslationUnitDecl and are handled separately (see AST example below). In the LLVM IR, metadata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIF...

...reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) Where "FileIncludeDecl" AST might contain other "FileIncludeDecl"/"MacroDecl" ASTs. These two new AST DECLs are not part of TranslationUnitDecl and are handled separately (see AST example below). In the LLVM IR, metadata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIF...

...reasonable to wire up the CGDebugInfo directly to the PPCallbacks, if it isn't already? (perhaps it is already wired up for other reasons?) Where "FileIncludeDecl" AST might contain other "FileIncludeDecl"/"MacroDecl" ASTs. These two new AST DECLs are not part of TranslationUnitDecl and are handled separately (see AST example below). In the LLVM IR, metadata debug info will be extended to support new DIs as well: "DIMacro", "DIFileInclude", and "MacroNode". The last, is needed as we cannot use DINode as a base class of "DIMacro" and DIF...

...directly to the PPCallbacks, if it isn't already? (perhaps > it is already wired up for other reasons?) > > > > Where "FileIncludeDecl" AST might contain other > "FileIncludeDecl"/"MacroDecl" ASTs. > > These two new AST DECLs are not part of TranslationUnitDecl and are > handled separately (see AST example below). > > > > In the LLVM IR, metadata debug info will be extended to support new DIs as > well: > > "DIMacro", "DIFileInclude", and "MacroNode". > > The last, is needed as we cannot use DINo...

...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 sloc>> <invalid sloc> |-TypedefDecl 0x8e41fe8 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128' | `-BuiltinType 0x8e41d00 '__int128' |-TypedefDecl 0x8e42048 <<invalid sloc>> <invalid sloc> implici...

...it isn't already? (perhaps >> it is already wired up for other reasons?) >> >> >> >> Where "FileIncludeDecl" AST might contain other >> "FileIncludeDecl"/"MacroDecl" ASTs. >> >> These two new AST DECLs are not part of TranslationUnitDecl and are >> handled separately (see AST example below). >> >> >> >> In the LLVM IR, metadata debug info will be extended to support new DIs >> as well: >> >> "DIMacro", "DIFileInclude", and "MacroNode". >> >> T...

...gt;>> it is already wired up for other reasons?) >>> >>> >>> >>> Where "FileIncludeDecl" AST might contain other >>> "FileIncludeDecl"/"MacroDecl" ASTs. >>> >>> These two new AST DECLs are not part of TranslationUnitDecl and are >>> handled separately (see AST example below). >>> >>> >>> >>> In the LLVM IR, metadata debug info will be extended to support new DIs >>> as well: >>> >>> "DIMacro", "DIFileInclude", and "Macr...