diff options
author | Simon Pilgrim <llvm-dev@redking.me.uk> | 2021-07-09 11:48:25 +0100 |
---|---|---|
committer | Simon Pilgrim <llvm-dev@redking.me.uk> | 2021-07-09 12:07:33 +0100 |
commit | 9dbeac16ba9b7a5121c0ce5ba8b7eb5c46ce2b15 (patch) | |
tree | e736493b3812007860183f600c922d1c4cac975c /llvm/lib/Transforms/Utils/Local.cpp | |
parent | 9c5e65691e129a816ea4bba10be103ca67172ca5 (diff) | |
download | llvm-9dbeac16ba9b7a5121c0ce5ba8b7eb5c46ce2b15.zip llvm-9dbeac16ba9b7a5121c0ce5ba8b7eb5c46ce2b15.tar.gz llvm-9dbeac16ba9b7a5121c0ce5ba8b7eb5c46ce2b15.tar.bz2 |
[X86] ReplaceNodeResults - fp_to_sint/uint - manually widen v2i32 results to let us add AssertSext/AssertZext
Its proving tricky to move this to the generic legalizer code, so manually insert the v2i32 subvector into v4i32, insert the AssertSext/AssertZext node, then extract the subvector again.
This avoids masks in the truncation/pack code, which means we avoid a PSHUFB in the fp_to_sint/uint code for sub-128 bit types (specific targets can still combine the packs to a pshufb if they have fast variable per-lane shuffles).
This was noticed when I was trying to improve fp_to_sint/uint costs with D103695 (and some targets had very high fp_to_sint costs due to the PSHUFB), so we can then update the fp_to_uint codegen from D89697.
Diffstat (limited to 'llvm/lib/Transforms/Utils/Local.cpp')
0 files changed, 0 insertions, 0 deletions