diff options
| author | Anna Zaks <ganna@apple.com> | 2013-04-03 21:34:12 +0000 |
|---|---|---|
| committer | Anna Zaks <ganna@apple.com> | 2013-04-03 21:34:12 +0000 |
| commit | d3254b446211d3f1a455c4f2247dc910df68d69f (patch) | |
| tree | ecd3f27ff5bdb9929437c74ad448005e13f07a75 /lldb/source/Interpreter/CommandObjectRegexCommand.cpp | |
| parent | f24933f65e5687e92774b97894142dd8dc709d66 (diff) | |
| download | bcm5719-llvm-d3254b446211d3f1a455c4f2247dc910df68d69f.tar.gz bcm5719-llvm-d3254b446211d3f1a455c4f2247dc910df68d69f.zip | |
[analyzer] Allow tracknullOrUndef look through the ternary operator even when condition is unknown
Improvement of r178684 and r178685.
Jordan has pointed out that I should not rely on the value of the condition to know which expression branch
has been taken. It will not work in cases the branch condition is an unknown value (ex: we do not track the constraints for floats).
The better way of doing this would be to find out if the current node is the right or left successor of the node
that has the ternary operator as a terminator (which is how this is done in other places, like ConditionBRVisitor).
llvm-svn: 178701
Diffstat (limited to 'lldb/source/Interpreter/CommandObjectRegexCommand.cpp')
0 files changed, 0 insertions, 0 deletions
