search for: typedefdecl

...nt 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> implicit __uint128_t 'unsigned __int128' | `-BuiltinType 0x8e41d20 'u...

...n which they are allocated. It is easy for the allocator to identify if a pointer belongs to that allocator, and if so, deteremine which slab it belongs to and at what offset the object is in that slab. Therefore it is possible to identify the object by its (slab index, offset) pair. Eg., "TypedefDecl 0:528" (you already memorized it) instead of "TypedefDecl 0x7f80a28325e0". This could be applied to all sorts of objects that live in BumpPtrAllocators. In order to compute such identifier, we only need access to the object and to the allocator. No additional memory is used to st...

...l 0x11c0318 <myfile.h:1:1> col:1 | |-MacroDecl 0x11c0348 <line:4:8> col:8 M1 undefined | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128' |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit __uint128_t 'unsigned __int128' |-TypedefDecl 0xd6c3c8 <<invalid sloc>> <invalid sloc> implic...

...er in which they are allocated. It is easy for the allocator to identify if a pointer belongs to that allocator, and if so, deteremine which slab it belongs to and at what offset the object is in that slab. Therefore it is possible to identify the object by its (slab index, offset) pair. Eg., "TypedefDecl 0:528" (you already memorized it) instead of "TypedefDecl 0x7f80a28325e0". This could be applied to all sorts of objects that live in BumpPtrAllocators. >> >> In order to compute such identifier, we only need access to the object and to the allocator. No additional memor...

...l 0x11c0318 <myfile.h:1:1> col:1 | |-MacroDecl 0x11c0348 <line:4:8> col:8 M1 undefined | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128' |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit __uint128_t 'unsigned __int128' |-TypedefDecl 0xd6c3c8 <<invalid sloc>> <invalid sloc> implic...

...l 0x11c0318 <myfile.h:1:1> col:1 | |-MacroDecl 0x11c0348 <line:4:8> col:8 M1 undefined | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128' |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit __uint128_t 'unsigned __int128' |-TypedefDecl 0xd6c3c8 <<invalid sloc>> <invalid sloc> implic...

...l 0x11c0318 <myfile.h:1:1> col:1 | |-MacroDecl 0x11c0348 <line:4:8> col:8 M1 undefined | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128' |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit __uint128_t 'unsigned __int128' |-TypedefDecl 0xd6c3c8 <<invalid sloc>> <invalid sloc> implic...

...|-MacroDecl 0x11c0348 <line:4:8> col:8 M1 undefined > > | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined > > `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined > > TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> > > |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit __int128_t > '__int128' > > |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit > __uint128_t 'unsigned __int128' > > |-TypedefDecl 0xd6c3c8 <<invalid sloc>&g...

...4:8> col:8 M1 undefined >> >> | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined >> >> `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined >> >> TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> >> >> |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit >> __int128_t '__int128' >> >> |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit >> __uint128_t 'unsigned __int128' >> >> |-TypedefDecl 0xd6c3c8 &l...

...gt;> >>> | `-MacroDecl 0x11c03a0 <line:5:9> col:9 M1 defined >>> >>> `-MacroDecl 0x11c03f8 <mainfile.c:3:9> col:9 M2 defined >>> >>> TranslationUnitDecl 0xd6c078 <<invalid sloc>> <invalid sloc> >>> >>> |-TypedefDecl 0xd6c330 <<invalid sloc>> <invalid sloc> implicit >>> __int128_t '__int128' >>> >>> |-TypedefDecl 0xd6c370 <<invalid sloc>> <invalid sloc> implicit >>> __uint128_t 'unsigned __int128' >>> >>> |...

I'm in the process of writing a clang-tidy check that concerns the position of the "const" keyword. The check should either enforce "T const" or "const T", based on a flag. Naturally, this should extend to all sorts of variations and qualifiers, e.g., X<const T&, Y const*> const&. My approach is to first find the right AST matcher expression to flag