aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Target/PowerPC/Disassembler/PPCDisassembler.cpp
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-06-10 16:59:28 +0000
committerCraig Topper <craig.topper@intel.com>2019-06-10 16:59:28 +0000
commit8e1f3a0538574d97a660c85cb89a487e6d2c2a38 (patch)
tree0121cd097911a2d7441069241e56cf41496666a8 /llvm/lib/Target/PowerPC/Disassembler/PPCDisassembler.cpp
parentc650a9084fcb24bfc342d97d74d343f145664bd2 (diff)
downloadllvm-8e1f3a0538574d97a660c85cb89a487e6d2c2a38.zip
llvm-8e1f3a0538574d97a660c85cb89a487e6d2c2a38.tar.gz
llvm-8e1f3a0538574d97a660c85cb89a487e6d2c2a38.tar.bz2
[X86] Attempt to make the Intel core CPU inheritance a little more readable and maintainable
The recently added cooperlake CPU has made our already ugly switch statement even worse. There's a CPU exclusion list around the bf16 feature in the cooper lake block. I worry that we'll have to keep adding new CPUs to that until bf16 intercepts a client space CPU. We have several other exclusion lists in other parts of the switch due to skylakeserver, cascadelake, and cooperlake not having sgx. Another for cannonlake not having clwb but having all other features from skx. This removes all these special ifs at the cost of some duplication of features and a goto. I've copied all of the skx features into either cannonlake or icelakeclient(for clwb). And pulled sklyakeserver, cascadelake, and cooperlake out of the main inheritance chain into their own chain. At the end of skylakeserver we merge back into the main chain at skylakeclient but below sgx. I think this is at least easier to follow. Differential Revision: https://reviews.llvm.org/D63018 llvm-svn: 362965
Diffstat (limited to 'llvm/lib/Target/PowerPC/Disassembler/PPCDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions