diff options
author | Pat Gavlin <pgavlin@gmail.com> | 2017-05-19 12:45:45 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-05-19 12:45:45 -0700 |
commit | f993896e20cb303deb7f5c4021901446f07dd7df (patch) | |
tree | 20db5a9a22beeec20c627b673b1e78fc2e38c15b /verify-so.sh | |
parent | dde23243ab8ca1626d918a6143e7717c58246459 (diff) | |
download | coreclr-f993896e20cb303deb7f5c4021901446f07dd7df.tar.gz coreclr-f993896e20cb303deb7f5c4021901446f07dd7df.tar.bz2 coreclr-f993896e20cb303deb7f5c4021901446f07dd7df.zip |
Remove `GTF_REVERSE_OPS` from LIR. (#10698)
In HIR, this flag indicates that the second operand to a binary node will execute before
the node's first operand. LIR, however, no longer determines ordering via use edges, so
this flag only affects the order in which operands to a node are considered. The sole
constraint on this use ordering is that for a given node, the same ordering must be used
in liveness, LSRA, and the code generator; this is due to the correspondence between
use ordering and spill/reload/last-use ordering. As a result, the reverse ops flag is
unnecessary and rather unhelpful in LIR, causing little more than a bit of extra complexity
throughout the backend.
This change removes `GTF_REVERSE_OPS` from LIR by clearing this flag during rationalize
and verifying that it remains clear in `LIR::CheckLIR`. We could reuse this bit for an
additional backend-specific purpose in the future with a bit more work in the checker.
Diffstat (limited to 'verify-so.sh')
0 files changed, 0 insertions, 0 deletions