search for: reg16393

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

Did you mean: reg16390
2010 Jul 28
3
[LLVMdev] Subregister coalescing
...alescing between its subregs and the load destinations. Is there a way to solve this? As an alternate approach, I also tried to do a custom InstrInserter that ended with the correct code just after MI emission: 68 %reg16392<def> = LDWr %reg16384<kill>, 0; mem:LD4[<unknown>] 76 %reg16393<def> = LDWr %reg16386<kill>, 0; mem:LD4[<unknown>] 84 %reg16394<def> = LDWr %reg16387<kill>, 0; mem:LD4[<unknown>] 92 %reg16395<def> = LDWr %reg16388<kill>, 0; mem:LD4[<unknown>] 132 %reg16400:1<def,dead> = MOVI32rr %reg16392<kill> 1...
2010 Nov 27
3
[LLVMdev] Register Pairing
...%reg16391<def> = ADDRdRr %reg16388, %reg16387<kill>, %SREG<imp-def>; GPR8:%reg16391,16388,16387 // ADD LO BYTES %reg16392<def> = ADCRdRr %reg16390, %reg16389<kill>, %SREG<imp-def,dead>, %SREG<imp-use>; GPR8:%reg16392,16390,16389 // ADDC HI BYTES %reg16393<def> = REG_SEQUENCE %reg16391<kill>, ssub_0, %reg16392<kill>, ssub_1; WDREGS:%reg16393 GPR8:%reg16391,16392 // COMBINE INTO REG PAIR AGAIN %R25R24<def> = COPY %reg16393; WDREGS:%reg16393 // COPY REG PAIR INTO RETURN REG. RET This is fine until we get to the register...
2010 Jul 28
0
[LLVMdev] Subregister coalescing
...n to do that. Your machine code looks like you are using 2.7. > As an alternate approach, I also tried to do a custom InstrInserter that > ended with the correct code just after MI emission: > > 68 %reg16392<def> = LDWr %reg16384<kill>, 0; mem:LD4[<unknown>] > 76 %reg16393<def> = LDWr %reg16386<kill>, 0; mem:LD4[<unknown>] > 84 %reg16394<def> = LDWr %reg16387<kill>, 0; mem:LD4[<unknown>] > 92 %reg16395<def> = LDWr %reg16388<kill>, 0; mem:LD4[<unknown>] > 132 %reg16400:1<def,dead> = MOVI32rr %reg1639...
2010 Nov 08
2
[LLVMdev] [LLVMDev] Register Allocation and copy instructions
...ived from LLVM BB %bb Predecessors according to CFG: BB#0 BB#1 %reg16386<def> = PHI %reg16385, <BB#0>, %reg16394, <BB#1>; GR16:%reg16386,16385,16394 %reg16387<def> = PHI %reg16384, <BB#0>, %reg16398, <BB#1>; GR16:%reg16387,16384,16398 %reg16393<def> = MOV16ri 1; GR16:%reg16393 %reg16398<def> = COPY %reg16387; GR16:%reg16398,16387 %reg16398<def> = XOR16rr %reg16398, %reg16386, %EFLAGS<imp-def>; GR16:%reg16398,16386 %reg16397<def> = COPY %reg16398; GR16:%reg16397,16398 %reg16397&...