summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2020-01-14 09:53:50 +0100
committerRaphael Isemann <teemperor@gmail.com>2020-01-14 09:55:34 +0100
commitf18370fe0e7576fb9947e49d66f7a6962c6822ce (patch)
tree8689dfc3c0e59d3e0867a58d426258af4490960c /lldb/packages/Python/lldbsuite/test
parent61b6a4e82653e1209126404d33ad20a268f55db1 (diff)
downloadbcm5719-llvm-f18370fe0e7576fb9947e49d66f7a6962c6822ce.tar.gz
bcm5719-llvm-f18370fe0e7576fb9947e49d66f7a6962c6822ce.zip
[lldb] Don't defend against internal LLVM errors in IRInterpreter
Summary: Whenever we cast an LLVM instruction to one of its subclasses, we do a double check if the RTTI enum value actually allows us to cast the class. I don't see a way this can ever happen as even when LLVM's RTTI system has some corrupt internal state (which we probably should not test in the first place) we just reuse LLVM RTTI to do the second check. This also means that if we ever make an actual programming error in this function (e.g., have a enum value and then cast it to a different subclass), we just silently fall back to the JIT in our tests. We also can't test this code in any reasonable way. This removes the checks and uses `llvm::cast` instead which will raise a fatal error when casting fails. Reviewers: labath, mib Reviewed By: labath Subscribers: abidh, JDevlieghere, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D72596
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud