Displaying 2 results from an estimated 2 matches for "mv_ar16_ar16_lo16in32".
2017 Jun 27
4
Ok with mismatch between dead-markings in BUNDLE and bundled instructions?
...In our out-of-tree target we've been doing some bundling before register
allocation for quite some time now, and last night a new problem popped
up. What the fix should be depends on if this bundle is legal or not:
BUNDLE %vreg39<imp-def,dead>
* %vreg39:hiAcc<def> = mv_ar16_ar16_lo16In32 %vreg37
[...]
%vreg39 isn't used after the bundle so the dead-marking in the BUNDLE is
correct. However, the def in the actual bundled instruction defining
%vreg39 is not marked with dead.
Is the above bundle ok or not?
When the register allocator later tries to spill/reload %vreg3...
2017 Jun 27
5
Ok with mismatch between dead-markings in BUNDLE and bundled instructions?
...e target we've been doing some bundling before register allocation for quite some time now, and last night a new problem popped up. What the fix should be depends on if this bundle is legal or not:
>>
>> BUNDLE %vreg39<imp-def,dead>
>> * %vreg39:hiAcc<def> = mv_ar16_ar16_lo16In32 %vreg37
>> [...]
>>
>> %vreg39 isn't used after the bundle so the dead-marking in the BUNDLE is correct. However, the def in the actual bundled instruction defining %vreg39 is not marked with dead.
>>
>> Is the above bundle ok or not?
>
> As to whether...