search for: reg1053

Displaying 6 results from an estimated 6 matches for "reg1053".

Did you mean: reg1033
2008 Jan 16
4
[LLVMdev] LiveInterval Questions
...hat give a LiveRange a, a.valno->def, if valid, would be the same as a.start. But this is apparently not always the case. For example: Predecessors according to CFG: 0x839d130 (#3) 0x8462780 (#35) 308 %reg1051 = MOV64rr %reg1227<kill> 312 %reg1052 = MOV64rr %reg1228<kill> 316 %reg1053 = MOV64rr %reg1229<kill> 320 %reg1054 = MOV64rr %reg1230<kill> 324 %reg1055<dead> = LEA64r %reg1047, 1, %reg1053, 0 328 %reg1135 = MOVSX64rr32 %reg1025 332 %reg1136 = MOV64rr %reg1135<kill> 336 %reg1136 = ADD64ri32 %reg1136, -4, %EFLAGS<imp-def,dead> 340 TEST64rr %reg1...
2008 Jan 17
0
[LLVMdev] LiveInterval Questions
...t;def, if > valid, would be the same as a.start. But this is apparently not > always the case. For example: > > Predecessors according to CFG: 0x839d130 (#3) 0x8462780 (#35) > 308 %reg1051 = MOV64rr %reg1227<kill> > 312 %reg1052 = MOV64rr %reg1228<kill> > 316 %reg1053 = MOV64rr %reg1229<kill> > 320 %reg1054 = MOV64rr %reg1230<kill> > 324 %reg1055<dead> = LEA64r %reg1047, 1, %reg1053, 0 > 328 %reg1135 = MOVSX64rr32 %reg1025 > 332 %reg1136 = MOV64rr %reg1135<kill> > 336 %reg1136 = ADD64ri32 %reg1136, -4, %EFLAGS<imp-def,de...
2007 Jul 12
1
[LLVMdev] backend problem with LiveInterval::removeRange
...c8bf0 SU(1): 0x88c9640: i32 = ADDu 0x88c9c08, 0x88c9c08 SU(3): 0x88c8d68: ch = SW 0x88c9640, 0x88c9ba0, 0x88c89a8, 0x88c9c08:1 SU(2): 0x88c9b38: ch = J 0x88c8940, 0x88c8d68 Selected machine code: cond_true28: 0x88c8218, LLVM BB @0x88beca0, ID#9: Predecessors according to CFG: 0x88c8140 (#8) %reg1053 = LW 0, <fi#6> %reg1054 = ADDu %reg1053, %reg1053 SW %reg1054, 0, <fi#7> J mbb<bb38,0x88c8310> Successors according to CFG: 0x88c8310 (#11) Total amount of phi nodes to update: 0 Replacing.3 0x88c89a8: i32 = shl 0x88c8d28, 0x88c8940 With: 0x88c8d28: i32,ch = load 0x88c9060...
2008 Jan 17
0
[LLVMdev] LiveInterval Questions
...gt;def, if > valid, would be the same as a.start. But this is apparently not > always the case. For example: > > Predecessors according to CFG: 0x839d130 (#3) 0x8462780 (#35) > 308 %reg1051 = MOV64rr %reg1227<kill> > 312 %reg1052 = MOV64rr %reg1228<kill> > 316 %reg1053 = MOV64rr %reg1229<kill> > 320 %reg1054 = MOV64rr %reg1230<kill> > 324 %reg1055<dead> = LEA64r %reg1047, 1, %reg1053, 0 > 328 %reg1135 = MOVSX64rr32 %reg1025 > 332 %reg1136 = MOV64rr %reg1135<kill> > 336 %reg1136 = ADD64ri32 %reg1136, -4, %EFLAGS<imp-def,de...
2010 Sep 07
3
[LLVMdev] MachineMemOperand and dependence information
...xample, a single load instruction could be replicated three times. (before transformation) %reg1033<def> = LDR %reg1030, %reg0, 4100, pred:14, pred:%reg0; mem:LD4[%uglygep10] (after transformation) %reg1043<def> = LDR %reg1040, %reg0, 4100, pred:14, pred:%reg0; mem:LD4[%uglygep10] ... %reg1053<def> = LDR %reg1050, %reg0, 4100, pred:14, pred:%reg0; mem:LD4[%uglygep10] ... %reg1063<def> = LDR %reg1060, %reg0, 4100, pred:14, pred:%reg0; mem:LD4[%uglygep10] In this example, should mem:LD4[%uglygep10] be removed from the three instructions so that passes run later will not use de...
2004 Jun 22
3
[LLVMdev] Linearscan allocator bug?
...%reg1043, %reg1041 %reg1044 = - %ar7, 2 store %reg1044, %reg1029 %reg1045 = - %ar7, 3 store %reg1045, %reg1046 %reg1047 = - %ar7, 4 %reg1048 = move 0 store %reg1047, %reg1048 %reg1049 = - %ar7, 5 store %reg1049, %reg1050 %reg1051 = - %ar7, 6 %reg1052 = move 0 store %reg1051, %reg1052 %reg1053 = - %ar7, 7 store %reg1053, %reg1039 call <ga:printf> %ar7 = - %ar7, 8 %reg1054 = move %gr7 return shortcirc_done.1 (0x8065d90, LLVM BB @0x8060320): %reg1060 = phi %reg1032, mbb<shortcirc_next.0.selectcont.selectcont,0x8065c10> %reg1064 = phi %reg1035, mbb<shortcirc_next.0.se...