diff options
| author | Richard Smith <richard-llvm@metafoo.co.uk> | 2017-09-22 01:04:22 +0000 |
|---|---|---|
| committer | Richard Smith <richard-llvm@metafoo.co.uk> | 2017-09-22 01:04:22 +0000 |
| commit | aa6ce3414143594c496e634de199de0c4173e36f (patch) | |
| tree | 4d152b5100cb751e913de039e0a7f1dc08115cdb /lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp | |
| parent | fec5e10890076a5ab9615f655be8e085ee8a8b06 (diff) | |
| download | bcm5719-llvm-aa6ce3414143594c496e634de199de0c4173e36f.tar.gz bcm5719-llvm-aa6ce3414143594c496e634de199de0c4173e36f.zip | |
Fix tracking of whether a destructor would be deleted.
I've been unable to find any cases whose behavior is actually changed by this,
but only because an implicitly deleted destructor also results in it being
impossible to have a trivial (non-deleted) copy constructor, which the place
where this really matters (choosing whether to pass a class in registers)
happens to also check.
llvm-svn: 313948
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/main.cpp')
0 files changed, 0 insertions, 0 deletions
