search for: flagfwddecl

...uot;, ...} ; ... [public] [rvalue reference] I don't want to regress here. In `DIDescriptor`, the flags are described in an enum bitfield: FlagAccessibility = 1 << 0 | 1 << 1, FlagPrivate = 1, FlagProtected = 2, FlagPublic = 3, FlagFwdDecl = 1 << 2, FlagAppleBlock = 1 << 3, FlagBlockByrefStruct = 1 << 4, FlagVirtual = 1 << 5, FlagArtificial = 1 << 6, FlagExplicit = 1 << 7, FlagPrototyped = 1 << 8, FlagObjcClassComp...

...BitcodeReader. I passed in a new flag indicating that we are parsing a module for function importing. Then when parsing a METADATA_COMPOSITE_TYPE, if we are importing a module I change the calls to buildODRType and GET_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 DIT...

...n a new flag indicating that we are parsing a module for function > importing. Then when parsing a METADATA_COMPOSITE_TYPE, if we are importing > a module I change the calls to buildODRType and GET_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) >...

...n a new flag indicating that we are parsing a module for function > importing. Then when parsing a METADATA_COMPOSITE_TYPE, if we are importing > a module I change the calls to buildODRType and GET_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) >...

On Wed, Feb 10, 2016 at 10:50 AM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> Is this change indeed intended as a visible API change to source code generating references to argument list values? If so, can you point me to a description of how I should change our code? Should I bug someone else about this problem? Should this API change be documented in

...> I don't want to regress here. > > In `DIDescriptor`, the flags are described in an enum bitfield: > > FlagAccessibility = 1 << 0 | 1 << 1, > FlagPrivate = 1, > FlagProtected = 2, > FlagPublic = 3, > FlagFwdDecl = 1 << 2, > FlagAppleBlock = 1 << 3, > FlagBlockByrefStruct = 1 << 4, > FlagVirtual = 1 << 5, > FlagArtificial = 1 << 6, > FlagExplicit = 1 << 7, > FlagPrototyped = 1 &lt...