search for: linkdefinedtypebodies

Displaying 4 results from an estimated 4 matches for "linkdefinedtypebodies".

2018 Mar 23
2
IRMover asserts "mapping to a source type" when repeatedly linking - usage or LLVM bug?
...'". 3) inlinining loads module "b", clones it, links module "b'" into "main1'". This module has a *non-opaque* definition of "t". Thus "t", as referenced by "main1'", gets its type "t" completed (via linkDefinedTypeBodies()). 4) "main2" module gets created 5) inlining clones module "a". As types are global to a context, "t" now has a body, *and* the body appears to be from the source module (actually "b'"). "mapping to a source type" is the result. As far...
2018 Mar 26
0
IRMover asserts "mapping to a source type" when repeatedly linking - usage or LLVM bug?
...3) inlinining loads module "b", clones it, links module "b'" into > "main1'". This module has a *non-opaque* definition of "t". Thus "t", > as referenced by "main1'", gets its type "t" completed (via > linkDefinedTypeBodies()). > 4) "main2" module gets created > 5) inlining clones module "a". As types are global to a context, "t" now > has a body, *and* the body appears to be from the source module > (actually "b'"). "mapping to a source type" is th...
2018 Mar 27
2
IRMover asserts "mapping to a source type" when repeatedly linking - usage or LLVM bug?
...loads module "b", clones it, links module "b'" into > > "main1'". This module has a *non-opaque* definition of "t". Thus "t", > > as referenced by "main1'", gets its type "t" completed (via > > linkDefinedTypeBodies()). > > 4) "main2" module gets created > > 5) inlining clones module "a". As types are global to a context, "t" now > > has a body, *and* the body appears to be from the source module > > (actually "b'"). "mapping to a sou...
2018 Mar 27
0
IRMover asserts "mapping to a source type" when repeatedly linking - usage or LLVM bug?
...module "b", clones it, links module "b'" into >>> "main1'". This module has a *non-opaque* definition of "t". Thus "t", >>> as referenced by "main1'", gets its type "t" completed (via >>> linkDefinedTypeBodies()). >>> 4) "main2" module gets created >>> 5) inlining clones module "a". As types are global to a context, "t" now >>> has a body, *and* the body appears to be from the source module >>> (actually "b'"). "mappin...