summaryrefslogtreecommitdiffstats
path: root/llvm/utils/TableGen/CodeGenInstruction.cpp
diff options
context:
space:
mode:
authorMichael Kruse <llvm@meinersbur.de>2015-12-22 23:25:11 +0000
committerMichael Kruse <llvm@meinersbur.de>2015-12-22 23:25:11 +0000
commit58fa3bb63a46fe99d5917ead7488d00958833882 (patch)
tree46745b15fded7bd2e0a3c380f32cb52c346d3165 /llvm/utils/TableGen/CodeGenInstruction.cpp
parentcc8f47ebc2bf945f2a6a787052c9839b9237005f (diff)
downloadbcm5719-llvm-58fa3bb63a46fe99d5917ead7488d00958833882.tar.gz
bcm5719-llvm-58fa3bb63a46fe99d5917ead7488d00958833882.zip
Do not store scalar accesses in InstructionToAccess
At code generation, scalar reads are generated before the other statement's instructions, respectively scalar writes after them, in contrast to array accesses which are "executed" with the instructions they are linked to. Therefore it makes sense to not map the scalar accesses to a place of execution. Follow-up patches will also remove some of the directs links from a scalar access to a single instruction, such that only having array accesses in InstructionToAccess ensures consistency. Differential Revision: http://reviews.llvm.org/D13676 llvm-svn: 256298
Diffstat (limited to 'llvm/utils/TableGen/CodeGenInstruction.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud