summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-03-05 01:14:25 +0000
committerCraig Topper <craig.topper@intel.com>2019-03-05 01:14:25 +0000
commit6a6ce5be84ce5e611002891f9cce8a61b88c1bc5 (patch)
tree16c22e4eac17ff8e515fc4d3f4a0445258a4e713 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
parentd82247cb804cfb48ae0e0bc354397b6be0ab60d4 (diff)
downloadbcm5719-llvm-6a6ce5be84ce5e611002891f9cce8a61b88c1bc5.tar.gz
bcm5719-llvm-6a6ce5be84ce5e611002891f9cce8a61b88c1bc5.zip
[X86] Reduce some patterns by using FP instructions for integer types even when AVX2 is available and execution domain fixing will do the right thing
We have quite a few cases of using FP instructions for integer operations when only AVX1 is available. Then we switch to integer instructions with AVX2. In a lot of these cases execution domain fixing will take care of turning FP instructions into integer if its profitable. With this patch we just keep on using the FP instructions even with AVX2. I've only handled some cases that don't require messing with patterns that are defined in the instruction definition. Those will require more subtle multiclass work possibly involving null_frag, hasSideEffects = 0, etc. Differential Revision: https://reviews.llvm.org/D58470 llvm-svn: 355361
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud