Displaying 3 results from an estimated 3 matches for "slotremap".
Did you mean:
slot_map
2013 Sep 29
2
[LLVMdev] StackColoring remaps debug info from unrelated functions
...Loc> pair. All infos of all functions reside in a
single map per module.
In lib/CodeGen/StackColoring.cpp:493 is the only place where this
information is updated (I am using LLVM 3.3, but the code seems to be
the same in trunk).
StackColoring::remapInstructions(DenseMap<int, int> &SlotRemap):
// Remap debug information that refers to stack slots.
MachineModuleInfo::VariableDbgInfoMapTy &VMap =
MMI->getVariableDbgInfo();
for (MachineModuleInfo::VariableDbgInfoMapTy::iterator VI = VMap.begin(),
VE = VMap.end(); VI != VE; ++VI) {
const MDNode *Var = VI->...
2013 Sep 30
0
[LLVMdev] StackColoring remaps debug info from unrelated functions
...infos of all functions reside in a single map per module.
>
> In lib/CodeGen/StackColoring.cpp:493 is the only place where this information is updated (I am using LLVM 3.3, but the code seems to be the same in trunk).
>
> StackColoring::remapInstructions(DenseMap<int, int> &SlotRemap):
>
> // Remap debug information that refers to stack slots.
> MachineModuleInfo::VariableDbgInfoMapTy &VMap = MMI->getVariableDbgInfo();
> for (MachineModuleInfo::VariableDbgInfoMapTy::iterator VI = VMap.begin(),
> VE = VMap.end(); VI != VE; ++VI) {
> const MD...
2020 May 06
2
Unexpected behavior found in Stack Coloring pass, need clarification
...ed last few lines of
runOnMachineFunction(..) method present in the StackColoring.cpp file. The
original source can be found here:
https://llvm.org/doxygen/StackColoring_8cpp_source.html
bool StackColoring::runOnMachineFunction(MachineFunction &Func) {
...
...
remapInstructions(SlotRemap);
+ bool markerCount = removeAllMarkers();
+ DenseMap<int, int>::iterator itr = SlotRemap.begin();
+ const AllocaInst *dInst = MFI->getObjectAllocation(itr->first);
+ LLVM_DEBUG(dbgs() << "Set break point here to inspect dInst\n");
+ return markerCount;
}
I&...