search for: ditypemap

...ET_OR_DISTINCT to instead create a type declaration: - pass in flags Flags|DINode::FlagFwdDecl - pass in nullptr for BaseType, Elements, VtableHolder, TemplateParams - pass in 0 for OffsetInBits Note that buildODRType will not mutate any existing DICompisiteType for that identifier found in the DITypeMap to a type declaration (FlagFwdDecl) though. This is good since we are sharing the DITypeMap with the original (destination) module, and we don't want to change any type definitions on the existing destination (importing) module to be type declarations when the same type is also in the source mo...

...gt; > - pass in flags Flags|DINode::FlagFwdDecl > > - pass in nullptr for BaseType, Elements, VtableHolder, TemplateParams > > - pass in 0 for OffsetInBits > > > > Note that buildODRType will not mutate any existing DICompisiteType for > that identifier found in the DITypeMap to a type declaration (FlagFwdDecl) > though. This is good since we are sharing the DITypeMap with the original > (destination) module, and we don't want to change any type definitions on > the existing destination (importing) module to be type declarations when > the same type is a...

...gt; > - pass in flags Flags|DINode::FlagFwdDecl > > - pass in nullptr for BaseType, Elements, VtableHolder, TemplateParams > > - pass in 0 for OffsetInBits > > > > Note that buildODRType will not mutate any existing DICompisiteType for > that identifier found in the DITypeMap to a type declaration (FlagFwdDecl) > though. This is good since we are sharing the DITypeMap with the original > (destination) module, and we don't want to change any type definitions on > the existing destination (importing) module to be type declarations when > the same type is a...

...eate a DICompositeType (CT) whose "scope:" is the DISubprogram (SP) for that function's definition. This SP is not part of the type graph, it's the actual definition that eventually describes the code. However, the CT has an ODR identifier, which means it will get uniqued by the DITypeMap. This seems wrong. If the function is defined in a header you can end up with two copies of this type, and their scope is completely unrelated. Here it is without using the type map: -- !0 = distinct !DICompileUnit() !1 = distinct !DISubprogram(name: "foo", unit: !0) !2 = distinct !DIC...

On Fri, Apr 15, 2016 at 4:04 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2016-Apr-15, at 14:53, David Blaikie <dblaikie at gmail.com> wrote: > > > > > > > >> On Fri, Apr 15, 2016 at 2:27 PM, Duncan P. N. Exon Smith < > dexonsmith at apple.com> wrote: > >> > >> > On 2016-Apr-15, at 10:27, David