summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/AMDGPU/AMDGPUSubtarget.cpp
diff options
context:
space:
mode:
authorUlrich Weigand <ulrich.weigand@de.ibm.com>2019-06-26 17:19:12 +0000
committerUlrich Weigand <ulrich.weigand@de.ibm.com>2019-06-26 17:19:12 +0000
commit4c86dd903265be9fd72a5ebf7c568a15f3cad0a6 (patch)
treefac06f3e4eb8ee5d8c60ed634d66888a79da325a /llvm/lib/Target/AMDGPU/AMDGPUSubtarget.cpp
parent03b2e2d9861efdcf6fd033b882d8b7b738428a49 (diff)
downloadbcm5719-llvm-4c86dd903265be9fd72a5ebf7c568a15f3cad0a6.tar.gz
bcm5719-llvm-4c86dd903265be9fd72a5ebf7c568a15f3cad0a6.zip
Allow matching extend-from-memory with strict FP nodes
This implements a small enhancement to https://reviews.llvm.org/D55506 Specifically, while we were able to match strict FP nodes for floating-point extend operations with a register as source, this did not work for operations with memory as source. That is because from regular operations, this is represented as a combined "extload" node (which is a variant of a load SD node); but there is no equivalent using a strict FP operation. However, it turns out that even in the absence of an extload node, we can still just match the operations explicitly, e.g. (strict_fpextend (f32 (load node:$ptr)) This patch implements that method to match the LDEB/LXEB/LXDB SystemZ instructions even when the extend uses a strict-FP node. llvm-svn: 364450
Diffstat (limited to 'llvm/lib/Target/AMDGPU/AMDGPUSubtarget.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud