llvm-capstone

mirror of https://github.com/capstone-engine/llvm-capstone.git synced 2025-03-04 00:20:14 +00:00

Go to file

Jordan Rose a4309c941c [analyzer] Treat C++ 'throw' as a sink.

Our current handling of 'throw' is all CFG-based: it jumps to a 'catch' block
if there is one and the function exit block if not. But this doesn't really
get the right behavior when a function is inlined: execution will continue on
the caller's side, which is always the wrong thing to do.

Even within a single function, 'throw' completely skips any destructors that
are to be run. This is essentially the same problem as @finally -- a CFGBlock
that can have multiple entry points, whose exit points depend on whether it
was entered normally or exceptionally.

Representing 'throw' as a sink matches our current (non-)handling of @throw.
It's not a perfect solution, but it's better than continuing analysis in an
inconsistent or even impossible state.

<rdar://problem/12113713>

llvm-svn: 162157

2012-08-18 00:30:23 +00:00

clang

[analyzer] Treat C++ 'throw' as a sink.

2012-08-18 00:30:23 +00:00

clang-tools-extra

Fixed some renaming detritus in the comments, and an unused variable warning. Thanks to David Blaikie and Manuel Klimek for the comments

2012-08-16 17:47:06 +00:00

compiler-rt

tsan: Non-executable stack for hand-coded assembly

2012-08-17 18:05:28 +00:00

debuginfo-tests

Fix this for gdb 7.4.