aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Object/ELFObjectFile.cpp
diff options
context:
space:
mode:
authorSjoerd Meijer <sjoerd.meijer@arm.com>2019-05-30 08:07:06 +0000
committerSjoerd Meijer <sjoerd.meijer@arm.com>2019-05-30 08:07:06 +0000
commit5857bf5d1e5a5ffe5ae51a38514ee55495c0cc69 (patch)
tree972015e6023e006e209274415c36d602d9267d75 /llvm/lib/Object/ELFObjectFile.cpp
parent9b8a0d7110e97db67f48368ee623d06cbb6075a5 (diff)
downloadllvm-5857bf5d1e5a5ffe5ae51a38514ee55495c0cc69.zip
llvm-5857bf5d1e5a5ffe5ae51a38514ee55495c0cc69.tar.gz
llvm-5857bf5d1e5a5ffe5ae51a38514ee55495c0cc69.tar.bz2
[ARM] Add an MVE execution domain
MVE architecturally specifies a 'beat' system in which a vector instruction executed now will complete its actual operation over the next four cycles, so it can overlap with the execution of the previous and next MVE instruction. This makes it generally an advantage to avoid moving values back and forth between MVE registers and anywhere else, if there's any sensible way to do the same processing in whatever register type the values already occupied. That's just what the 'execution domain' system is supposed to achieve. So here we add a new execution domain which will contain all the MVE vector instructions when they are added. Patch by: Simon Tatham Differential Revision: https://reviews.llvm.org/D60703 llvm-svn: 362068
Diffstat (limited to 'llvm/lib/Object/ELFObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions