Displaying 3 results from an estimated 3 matches for "vsub32_0".
Did you mean:
vsub32_1
2017 Feb 02
3
Register allocator behaves differently when compiling with and without -g
...asic block looks like this:
32B %vreg29<def> = LDImm 1; REG1:%vreg29
36B %vreg44<def> = LDImm 1103515245; REG1:%vreg44
40B %vreg143:vsub32_1<def,read-undef> = LDImm 0; REG2:%vreg143
44B %vreg68<def> = LDImm 12345; REG1:%vreg68
64B %vreg143:vsub32_0<def> = COPY %vreg143:vsub32_1; REG2:%vreg143
72B %vreg78<def> = LDImm 32; REG1:%vreg78
But when I specify -g, this becomes:
32B %vreg29<def> = LDImm 1; REG1:%vreg29 dbg:path/to/source:9:34 @[
path/to/source:25:13 ]
36B %vreg44<def> = LDImm 1103515245;...
2017 Feb 02
2
Register allocator behaves differently when compiling with and without -g
...t;
> 32B %vreg29<def> = LDImm 1; REG1:%vreg29
> 36B %vreg44<def> = LDImm 1103515245; REG1:%vreg44
> 40B %vreg143:vsub32_1<def,read-undef> = LDImm 0; REG2:%vreg143
> 44B %vreg68<def> = LDImm 12345; REG1:%vreg68
> 64B %vreg143:vsub32_0<def> = COPY %vreg143:vsub32_1; REG2:%vreg143
> 72B %vreg78<def> = LDImm 32; REG1:%vreg78
>
> But when I specify -g, this becomes:
>
> 32B %vreg29<def> = LDImm 1; REG1:%vreg29 dbg:path/to/source:9:34 @[ path/to/source:25:13 ]
> 36B %vreg44&l...
2017 Feb 02
2
Register allocator behaves differently when compiling with and without -g
...t;
> 32B %vreg29<def> = LDImm 1; REG1:%vreg29
> 36B %vreg44<def> = LDImm 1103515245; REG1:%vreg44
> 40B %vreg143:vsub32_1<def,read-undef> = LDImm 0; REG2:%vreg143
> 44B %vreg68<def> = LDImm 12345; REG1:%vreg68
> 64B %vreg143:vsub32_0<def> = COPY %vreg143:vsub32_1; REG2:%vreg143
> 72B %vreg78<def> = LDImm 32; REG1:%vreg78
>
> But when I specify -g, this becomes:
>
> 32B %vreg29<def> = LDImm 1; REG1:%vreg29 dbg:path/to/source:9:34 @[ path/to/source:25:13 ]
> 36B %vreg44&l...