search for: sig5069_nc

Displaying 2 results from an estimated 2 matches for "sig5069_nc".

Did you mean: sig5069_nl
2009 Mar 25
2
[LLVMdev] Register allocation of stack slots
...%R0<kill> 6 : Reusing SS#18 from physreg R0 for vreg1075 instead of reloading into physreg R0 7 : store <fi#9>, 0, %R0, Mem:ST(2,2) [sig5069_nl + 0] 8 : Reusing SS#18 from physreg R0 for vreg1076 instead of reloading into physreg R0 9 : store <fi#8>, 0, %R0, Mem:ST(2,2) [sig5069_nc + 0] 10: %R0<def> = movC 16384 11: PhysReg R0 clobbered, invalidating SS#18 12: store <fi#7>, 0, %R0<kill>, Mem:ST(2,2) [sig5069_re + 0] 13: Remembering SS#18 in physreg R0 14: %R0<def> = load <fi#18>, 0 If I interpret the log correctly: -R0 is used to i...
2009 Mar 25
0
[LLVMdev] Register allocation of stack slots
...SS#18 from physreg R0 for vreg1075 instead of reloading > into physreg R0 > 7 : store <fi#9>, 0, %R0, Mem:ST(2,2) [sig5069_nl + 0] > 8 : Reusing SS#18 from physreg R0 for vreg1076 instead of reloading > into physreg R0 > 9 : store <fi#8>, 0, %R0, Mem:ST(2,2) [sig5069_nc + 0] > 10: %R0<def> = movC 16384 > 11: PhysReg R0 clobbered, invalidating SS#18 > 12: store <fi#7>, 0, %R0<kill>, Mem:ST(2,2) [sig5069_re + 0] > 13: Remembering SS#18 in physreg R0 > 14: %R0<def> = load <fi#18>, 0 > > If I interpret t...