summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/interpreter/TestCommandInterpreterAPI.py
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2017-03-14 16:32:27 +0000
committerVedant Kumar <vsk@apple.com>2017-03-14 16:32:27 +0000
commitf2d04e628ddffadbb4fd5b2456bba2250fb1acd7 (patch)
tree93c3e3f2cf4a9a83e20ad605920eb59f5183c4bd /lldb/packages/Python/lldbsuite/test/python_api/interpreter/TestCommandInterpreterAPI.py
parent1c8c6a457ddfc61570c03293742c17559158532f (diff)
downloadbcm5719-llvm-f2d04e628ddffadbb4fd5b2456bba2250fb1acd7.tar.gz
bcm5719-llvm-f2d04e628ddffadbb4fd5b2456bba2250fb1acd7.zip
[ubsan] Add diagnostic handlers for nullability errors
Add 'nullability_arg' and 'nullability_return' diagnostic handlers, and also add a TypeCheckKind for null assignments to _Nonnull. With this in place, we can update clang to use the nicer handlers for nullability diagnostics. The alternative to this approach is to update the existing 'nonnull_arg' and 'nonnull_return' handlers to accept a boolean parameter. However, versioning the existing handlers would cause code size bloat, and the complexity cost of introducing new handlers into the runtime is low. I will add tests for this, and all of -fsanitize=nullability, into check-ubsan once the clang side of the changes is in. llvm-svn: 297748
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/interpreter/TestCommandInterpreterAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud