Displaying 6 results from an estimated 6 matches for "fladd_a32_a32_a32".
2017 Sep 26
0
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...gments. The reason the above verification failure is not hit at that point seems to be related to the FIXME in the following snippet from ConnectedVNInfoEqClasses::Classify():
That dump seems to be well before greedy runs, isn't it?
At a first glance the odd thing there is that the operand of fladd_a32_a32_a32 is rewritten from vreg77 to vreg76, but the vreg77 operand of the BUNDLE is not. Maybe you can find out why that is?
- Matthias
2017 Sep 26
2
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...attached log contains -print-before-all
-print-after-all and -debug output starting with the coalescer pass.
The verification failure is right after the first pass of
MachineCopyPropagation which runs after the greedy allocator.
> At a first glance the odd thing there is that the operand of fladd_a32_a32_a32 is rewritten from vreg77 to vreg76, but the vreg77 operand of the BUNDLE is not. Maybe you can find out why that is?
Sorry, I should have pointed this out before: because the loop over
instructions in MachineCopyPropagation is only visiting the BUNDLE
instructions themselves (i.e. it does not vi...
2017 Sep 26
2
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
Hi all,
Mikael reported a machine verification failure in his out-of-tree target
with the MachineCopyPropagation changes to forward registers (which is
currently reverted). The verification in question is:
*** Bad machine code: Multiple connected components in live interval ***
- function: utils_la_suite_matmul_ref
- interval: %vreg77
2017 Sep 26
0
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...gation which runs after the greedy allocator.
The copy propagation seemed to be working on vregs. This was extra confusing as D30751 seems to be currently reverted from trunk so I couldn't find references to that code.
>
>> At a first glance the odd thing there is that the operand of fladd_a32_a32_a32 is rewritten from vreg77 to vreg76, but the vreg77 operand of the BUNDLE is not. Maybe you can find out why that is?
>
> Sorry, I should have pointed this out before: because the loop over instructions in MachineCopyPropagation is only visiting the BUNDLE instructions themselves (i.e. it doe...
2017 Sep 27
2
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...fication error is
the last problem keeping me from re-enabling the copy forwarding patch
(I can send you my latest rebased version, but I don't think it is
relevant to this problem. See below).
>>
>>> At a first glance the odd thing there is that the operand of
>>> fladd_a32_a32_a32 is rewritten from vreg77 to vreg76, but the vreg77
>>> operand of the BUNDLE is not. Maybe you can find out why that is?
>>
>> Sorry, I should have pointed this out before: because the loop over
>> instructions in MachineCopyPropagation is only visiting the BUNDLE
>...
2017 Sep 27
0
[MachineCopyPropagation] Issue with register forwarding/allocation/verifier in out-of-tree target
...erification error is the last problem keeping me from re-enabling the copy forwarding patch (I can send you my latest rebased version, but I don't think it is relevant to this problem. See below).
>
>>>
>>>> At a first glance the odd thing there is that the operand of fladd_a32_a32_a32 is rewritten from vreg77 to vreg76, but the vreg77 operand of the BUNDLE is not. Maybe you can find out why that is?
>>>
>>> Sorry, I should have pointed this out before: because the loop over instructions in MachineCopyPropagation is only visiting the BUNDLE instructions themsel...