aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/StringMap.cpp
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2020-04-12 10:26:43 -0400
committerSanjay Patel <spatel@rotateright.com>2020-04-12 10:26:43 -0400
commitd04db4825a4d5f7fe298811a9a1644ae87748c6c (patch)
tree08995fb00f63eb75e5a364e3a84b1e819dd9b45c /llvm/lib/Support/StringMap.cpp
parentc23cbefd9d73e8551b0c8b6cc3f14bb6b067ca92 (diff)
downloadllvm-d04db4825a4d5f7fe298811a9a1644ae87748c6c.zip
llvm-d04db4825a4d5f7fe298811a9a1644ae87748c6c.tar.gz
llvm-d04db4825a4d5f7fe298811a9a1644ae87748c6c.tar.bz2
[x86] use vector instructions to lower FP->int->FP casts
As discussed in PR36617: https://bugs.llvm.org/show_bug.cgi?id=36617#c13 ...we can avoid the likely slow round-trip from XMM to GPR to XMM by using the vector versions of the convert instructions. Based on experimental results from recent Intel/AMD chips, we don't need to worry about triggering denorm stalls while operating on garbage data in the high lanes with convert instructions, so this is expected to always be as good or better perf than the scalar instruction equivalent. FP exceptions are also not a concern because strict code should not be using the regular SDAG opcodes. Differential Revision: https://reviews.llvm.org/D77895
Diffstat (limited to 'llvm/lib/Support/StringMap.cpp')
0 files changed, 0 insertions, 0 deletions