summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorMichael Kruse <llvm@meinersbur.de>2017-05-04 15:22:57 +0000
committerMichael Kruse <llvm@meinersbur.de>2017-05-04 15:22:57 +0000
commiteedae7630aeb02d6d2184e511802e600764bcc23 (patch)
tree5cdaf4d20ec0a0d42d3e56fe45a99bd5034d1369 /lldb/packages/Python/lldbsuite/test
parent4ef0370e6dbd6fb995eb89ad943a93e0995aed44 (diff)
downloadbcm5719-llvm-eedae7630aeb02d6d2184e511802e600764bcc23.tar.gz
bcm5719-llvm-eedae7630aeb02d6d2184e511802e600764bcc23.zip
Introduce VirtualUse. NFC.
If a ScopStmt references a (scalar) value, there are multiple possibilities where this value can come. The decision about what kind of use it is must be handled consistently at different places, which can be error-prone. VirtualUse is meant to centralize the handling of the different types of value uses. This patch makes ScopBuilder and CodeGeneration use VirtualUse. This already helps to show inconsistencies with the value handling. In order to keep this patch NFC, exceptions to the general rules are added. These might be fixed later if they turn to problems. Overall, this should result in fewer post-codegen IR-verification errors, but instead assertion failures in `getNewValue` that are closer to the actual error. Differential Revision: https://reviews.llvm.org/D32667 llvm-svn: 302157
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud