Displaying 2 results from an estimated 2 matches for "reg1631".
Did you mean:
reg16391
2008 May 28
3
[LLVMdev] Possible VirtRegMap Bug
...mapped "
00152 "virtual register");
00153 Virt2PhysMap[virtReg] = physReg;
00154 }
Note that this doesn't clear the stack slot or remat mappings.
In the particular code I'm looking at, linear scan spills an interval and
one of the intervals created (%reg1631) gets mark as rematerializable by
LiveIntervals:
00984 if (CreatedNewVReg) {
00985 if (DefIsReMat) {
00986 vrm.setVirtIsReMaterialized(NewVReg, ReMatDefMI/*, CanDelete*/);
00987 if (ReMatIds[VNI->id] == VirtRegMap::MAX_STACK_SLOT) {
00988 // Each valnum may...
2008 May 30
0
[LLVMdev] Possible VirtRegMap Bug
...virtual register");
> 00153 Virt2PhysMap[virtReg] = physReg;
> 00154 }
>
> Note that this doesn't clear the stack slot or remat mappings.
>
> In the particular code I'm looking at, linear scan spills an
> interval and
> one of the intervals created (%reg1631) gets mark as
> rematerializable by
> LiveIntervals:
>
> 00984 if (CreatedNewVReg) {
> 00985 if (DefIsReMat) {
> 00986 vrm.setVirtIsReMaterialized(NewVReg, ReMatDefMI/*,
> CanDelete*/);
> 00987 if (ReMatIds[VNI->id] == VirtRegMap::MAX_STACK_S...