diff options
author | David Majnemer <david.majnemer@gmail.com> | 2016-02-01 03:29:38 +0000 |
---|---|---|
committer | David Majnemer <david.majnemer@gmail.com> | 2016-02-01 03:29:38 +0000 |
commit | 784d4a455b42272c27a28e152d4c9f9e51293aa4 (patch) | |
tree | c442a6bde753d5a1220d8e68be0e0b3cb62afa7e /lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py | |
parent | 0dd4a9a9f44975d6f9ad301925dc89552a78eb0c (diff) | |
download | bcm5719-llvm-784d4a455b42272c27a28e152d4c9f9e51293aa4.tar.gz bcm5719-llvm-784d4a455b42272c27a28e152d4c9f9e51293aa4.zip |
Revert r258580 and r258581.
Those commits created an artificial edge from a cleanup to a synthesized
catchswitch in order to get the MSVC personality routine to execute
cleanups which don't cleanupret and are not wrapped by a catchswitch.
This worked well enough but is not a complete solution in situations
where there the cleanup infinite loops.
However, the real deal breaker behind this approach comes about from a
degenerate case where the cleanup is post-dominated by unreachable *and*
throws an exception. This ends poorly because the catchswitch will
inadvertently catch the exception.
Because of this we should go back to our previous behavior of not
executing certain cleanups (identical behavior with the Itanium ABI
implementation in clang, GCC and ICC).
N.B. I think this could be salvaged by making the catchpad rethrow the
exception and properly transforming throwing calls in the cleanup into
invokes.
llvm-svn: 259338
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/breakpoint/TestBreakpointAPI.py')
0 files changed, 0 insertions, 0 deletions