Displaying 2 results from an estimated 2 matches for "sig5069_r".
Did you mean:
sig5069_re
2009 Mar 25
2
[LLVMdev] Register allocation of stack slots
...l + 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 initialize the fi#18
-R0 is used to initialize fi #8 and #9 as well
-in line 10 and 12, another value is has to be used to init frame objects. R0 is allocated...
2009 Mar 25
0
[LLVMdev] Register allocation of stack slots
...rom 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 initialize the fi#18
> -R0 is used to initialize fi #8 and #9 as well
> -in line 10 and 12, another value is has to be used to in...