summaryrefslogtreecommitdiffstats
path: root/llvm/lib/ExecutionEngine
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-05-15 21:59:53 +0000
committerCraig Topper <craig.topper@intel.com>2019-05-15 21:59:53 +0000
commite43bdf144c9a56e465b28217dce3853ef76f5594 (patch)
tree95bd009831c3c378bc9df1dab848394ef9c51e85 /llvm/lib/ExecutionEngine
parent8b92bb359eb4e812bacbadca5df36d3212d8f391 (diff)
downloadbcm5719-llvm-e43bdf144c9a56e465b28217dce3853ef76f5594.tar.gz
bcm5719-llvm-e43bdf144c9a56e465b28217dce3853ef76f5594.zip
[X86] Delay creating index register negations during address matching until after we know for sure the match will succeed
If we're trying to match an LEA, its possible the LEA match will be deemed unprofitable. In which case the negation we created in matchAddress would be left dangling in the SelectionDAG. This could artificially increase use counts for other nodes in the DAG. Though I don't have an example of that. But it just seems like bad form to have dangling nodes in isel. Differential Revision: https://reviews.llvm.org/D61047 llvm-svn: 360823
Diffstat (limited to 'llvm/lib/ExecutionEngine')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud