summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
diff options
context:
space:
mode:
authorRoman Lebedev <lebedev.ri@gmail.com>2019-10-20 19:36:55 +0000
committerRoman Lebedev <lebedev.ri@gmail.com>2019-10-20 19:36:55 +0000
commit4b6223263a3c1fb98bc69e8eb6722d48e4eb9f49 (patch)
treee229e5036c67ff9002417820c2571e024e2543cf /lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py
parent926dae33ba658d72e9f8d76d004cd943d6280250 (diff)
downloadbcm5719-llvm-4b6223263a3c1fb98bc69e8eb6722d48e4eb9f49.tar.gz
bcm5719-llvm-4b6223263a3c1fb98bc69e8eb6722d48e4eb9f49.zip
[ConstantRange] makeGuaranteedNoWrapRegion(): `shl` support
Summary: If all the shifts amount are already poison-producing, then we can add more poison-producing flags ontop: https://rise4fun.com/Alive/Ocwi Otherwise, we should only consider the possible range of shift amts that don't result in poison. For unsigned range not not overflow, we must not shift out any set bits, and the actual limit for `x` can be computed by backtransforming the maximal value we could ever get out of the `shl` - `-1` through `lshr`. If the `x` is any larger than that then it will overflow. Likewise for signed range, but just in signed domain.. This is based on the general idea outlined by @nikic in https://reviews.llvm.org/D68672#1714990 Reviewers: nikic, sanjoy Reviewed By: nikic Subscribers: hiraditya, llvm-commits, nikic Tags: #llvm Differential Revision: https://reviews.llvm.org/D69217 llvm-svn: 375370
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/frame/TestFrames.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud