diff options
| author | Pierre Gousseau <pierregousseau14@gmail.com> | 2016-01-12 10:07:56 +0000 |
|---|---|---|
| committer | Pierre Gousseau <pierregousseau14@gmail.com> | 2016-01-12 10:07:56 +0000 |
| commit | e961b445ada499e233b8dbca58065d1372c32e88 (patch) | |
| tree | 0f3fd22843dfe3696b1913f975f5409a9b7bf17f /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py | |
| parent | ea8e8e9f97b22e6490898f495f24fd979b677dd0 (diff) | |
| download | bcm5719-llvm-e961b445ada499e233b8dbca58065d1372c32e88.tar.gz bcm5719-llvm-e961b445ada499e233b8dbca58065d1372c32e88.zip | |
[analyzer] Evaluate integral casts as cast symbols if truncations are detected.
The current workaround for truncations not being modelled is that the evaluation of integer to integer casts are simply bypassed and so the original symbol is used as the new casted symbol (cf SimpleSValBuilder::evalCastFromNonLoc).
This lead to the issue described in PR25078, as the RangeConstraintManager associates ranges with symbols.
The new evalIntegralCast method added by this patch wont bypass the cast if it finds the range of the symbol to be greater than the maximum value of the target type.
The fix to RangeSet::pin mentioned in the initial review will be committed separately.
Differential Revision: http://reviews.llvm.org/D12901
llvm-svn: 257464
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
