Displaying 12 results from an estimated 12 matches for "globalvaluematerializer".
2016 Jul 28
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...sponds to SGV. I found that newly created global variable has the extra ".1" added to the name of the SGV.
When this happens? I don't have a complete understanding but I observed that the same global value is materialized twice during the single invocation of IRLinker::run, once with GlobalValueMaterializer and once with LocalValueMaterializer. First, the global value
; Materializable
; Function Attrs: nounwind uwtable
define weak_odr void @foo(%1*) unnamed_addr #7 comdat($comdat1) align 2 personality i32 (...)* @__gxx_personality_v0 {}
(I renamed the function and comdat)
is materialized with Global...
2016 Jul 29
3
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...onds to SGV. I found that newly created global variable has the extra ".1" added to the name of the SGV.
When this happens? I don't have a complete understanding but I observed that the same global value is materialized twice during the single invocation of IRLinker::run, once with GlobalValueMaterializer and once with LocalValueMaterializer. First, the global value
Yes, the IRLinker will append an integer if it encounters a naming conflict. Normally this would happen in full LTO, but I guess is happening here since we are linking twice due to the alias.
; Materializable
; Function Attrs: noun...
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...created global variable has the
> extra ".1" added to the name of the SGV.
>
>
>
> When this happens? I don't have a complete understanding but I observed
> that the same global value is materialized twice during the single
> invocation of IRLinker::run, once with GlobalValueMaterializer and once
> with LocalValueMaterializer. First, the global value
>
Yes, the IRLinker will append an integer if it encounters a naming
conflict. Normally this would happen in full LTO, but I guess is happening
here since we are linking twice due to the alias.
>
>
> ; Materializable...
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...created global variable has the
> extra ".1" added to the name of the SGV.
>
>
>
> When this happens? I don't have a complete understanding but I observed
> that the same global value is materialized twice during the single
> invocation of IRLinker::run, once with GlobalValueMaterializer and once
> with LocalValueMaterializer. First, the global value
>
> Looking at the IRLinker, it appears this second (local) copy should only
be created if there was no copy already linked in from the same source
module:
In IRLinker::linkGlobalValueProto, we should find the DGV created by...
2016 Jul 29
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...onds to SGV. I found that newly created global variable has the extra ".1" added to the name of the SGV.
When this happens? I don't have a complete understanding but I observed that the same global value is materialized twice during the single invocation of IRLinker::run, once with GlobalValueMaterializer and once with LocalValueMaterializer. First, the global value
Looking at the IRLinker, it appears this second (local) copy should only be created if there was no copy already linked in from the same source module:
In IRLinker::linkGlobalValueProto, we should find the DGV created by the GlobalValue...
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...created global variable has the
> extra ".1" added to the name of the SGV.
>
>
>
> When this happens? I don't have a complete understanding but I observed
> that the same global value is materialized twice during the single
> invocation of IRLinker::run, once with GlobalValueMaterializer and once
> with LocalValueMaterializer. First, the global value
>
> Looking at the IRLinker, it appears this second (local) copy should only
> be created if there was no copy already linked in from the same source
> module:
>
>
>
> In IRLinker::linkGlobalValueProto, we sh...
2016 Jul 29
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...onds to SGV. I found that newly created global variable has the extra ".1" added to the name of the SGV.
When this happens? I don't have a complete understanding but I observed that the same global value is materialized twice during the single invocation of IRLinker::run, once with GlobalValueMaterializer and once with LocalValueMaterializer. First, the global value
Looking at the IRLinker, it appears this second (local) copy should only be created if there was no copy already linked in from the same source module:
In IRLinker::linkGlobalValueProto, we should find the DGV created by the GlobalVa...
2016 Jul 29
0
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...created global variable has the
> extra ".1" added to the name of the SGV.
>
>
>
> When this happens? I don't have a complete understanding but I observed
> that the same global value is materialized twice during the single
> invocation of IRLinker::run, once with GlobalValueMaterializer and once
> with LocalValueMaterializer. First, the global value
>
> Looking at the IRLinker, it appears this second (local) copy should only
> be created if there was no copy already linked in from the same source
> module:
>
>
>
> In IRLinker::linkGlobalValueProto, we sh...
2016 Jul 30
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...onds to SGV. I found that newly created global variable has the extra ".1" added to the name of the SGV.
When this happens? I don't have a complete understanding but I observed that the same global value is materialized twice during the single invocation of IRLinker::run, once with GlobalValueMaterializer and once with LocalValueMaterializer. First, the global value
Looking at the IRLinker, it appears this second (local) copy should only be created if there was no copy already linked in from the same source module:
In IRLinker::linkGlobalValueProto, we should find the DGV created by the GlobalVa...
2016 Jul 30
1
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...created global variable has the
> extra ".1" added to the name of the SGV.
>
>
>
> When this happens? I don't have a complete understanding but I observed
> that the same global value is materialized twice during the single
> invocation of IRLinker::run, once with GlobalValueMaterializer and once
> with LocalValueMaterializer. First, the global value
>
> Looking at the IRLinker, it appears this second (local) copy should only
> be created if there was no copy already linked in from the same source
> module:
>
>
>
> In IRLinker::linkGlobalValueProto, we sh...
2016 Aug 15
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...;.1" added to the name of the SGV.
>>>
>>>
>>>
>>> When this happens? I don't have a complete understanding but I observed
>>> that the same global value is materialized twice during the single
>>> invocation of IRLinker::run, once with GlobalValueMaterializer and once
>>> with LocalValueMaterializer. First, the global value
>>>
>>> Looking at the IRLinker, it appears this second (local) copy should only
>>> be created if there was no copy already linked in from the same source
>>> module:
>>>
>>...
2016 Aug 15
2
[ThinLTO] assert(GS != DefinedGlobals.end()) failed in FunctionImport.cpp
...created global variable has the
> extra ".1" added to the name of the SGV.
>
>
>
> When this happens? I don't have a complete understanding but I observed
> that the same global value is materialized twice during the single
> invocation of IRLinker::run, once with GlobalValueMaterializer and once
> with LocalValueMaterializer. First, the global value
>
> Looking at the IRLinker, it appears this second (local) copy should only
> be created if there was no copy already linked in from the same source
> module:
>
>
>
> In IRLinker::linkGlobalValueProto, we sh...