summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/AMDGPU/AMDGPUMachineFunction.cpp
diff options
context:
space:
mode:
authorSimon Tatham <simon.tatham@arm.com>2019-06-25 11:24:50 +0000
committerSimon Tatham <simon.tatham@arm.com>2019-06-25 11:24:50 +0000
commit4cf18c2849558d8aa0a8c3951b2532db18c0a65f (patch)
treeaaf7d86c55f620cbd6fd5085b0f6795f2b7551bb /llvm/lib/Target/AMDGPU/AMDGPUMachineFunction.cpp
parentd9654723ad8508583dc8a3c649e04a15cb82d386 (diff)
downloadbcm5719-llvm-4cf18c2849558d8aa0a8c3951b2532db18c0a65f.tar.gz
bcm5719-llvm-4cf18c2849558d8aa0a8c3951b2532db18c0a65f.zip
[ARM] Explicit lowering of half <-> double conversions.
If an FP_EXTEND or FP_ROUND isel dag node converts directly between f16 and f32 when the target CPU has no instruction to do it in one go, it has to be done in two steps instead, going via f32. Previously, this was done implicitly, because all such CPUs had the storage-only implementation of f16 (i.e. the only thing you can do with one at all is to convert it to/from f32). So isel would legalize the f16 into an f32 as soon as it saw it, by inserting an fp16_to_fp node (or vice versa), and then the fp_extend would already be f32->f64 rather than f16->f64. But that technique can't support a target CPU which has full f16 support but _not_ f64, such as some variants of Arm v8.1-M. So now we provide custom lowering for FP_EXTEND and FP_ROUND, which checks support for f16 and f64 and decides on the best thing to do given the combination of flags it gets back. Reviewers: dmgreen, samparker, SjoerdMeijer Subscribers: javed.absar, kristof.beyls, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D60692 llvm-svn: 364294
Diffstat (limited to 'llvm/lib/Target/AMDGPU/AMDGPUMachineFunction.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud