diff options
author | Hideto Ueno <uenoku.tokotoko@gmail.com> | 2020-01-15 15:25:52 +0900 |
---|---|---|
committer | Hideto Ueno <uenoku.tokotoko@gmail.com> | 2020-01-15 16:34:23 +0900 |
commit | 188f9a348dc545bf9a420d998ad37761bddd7285 (patch) | |
tree | a99a3f5ab790b7781c63fe9102890eacd9977db2 /clang/lib/Edit/RewriteObjCFoundationAPI.cpp | |
parent | b891490ceb390b9c9ccc93abf08c2c1bec50e340 (diff) | |
download | bcm5719-llvm-188f9a348dc545bf9a420d998ad37761bddd7285.tar.gz bcm5719-llvm-188f9a348dc545bf9a420d998ad37761bddd7285.zip |
[Attributor] AAValueConstantRange: Value range analysis using constant range
Summary:
This patch introduces `AAValueConstantRange`, which answers a possible range for integer value in a specific program point.
One of the motivations is propagating existing `range` metadata. (I think we need to change the situation that `range` metadata cannot be put to Argument).
The state is a tuple of `ConstantRange` and it is initialized to (known, assumed) = ([-∞, +∞], empty).
Currently, AAValueConstantRange is created in `getAssumedConstant` method when `AAValueSimplify` returns `nullptr`(worst state).
Supported
- BinaryOperator(add, sub, ...)
- CmpInst(icmp eq, ...)
- !range metadata
`AAValueConstantRange` is not intended to extend to polyhedral range value analysis.
Reviewers: jdoerfert, sstefan1
Reviewed By: jdoerfert
Subscribers: phosek, davezarzycki, baziotis, hiraditya, javed.absar, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D71620
Diffstat (limited to 'clang/lib/Edit/RewriteObjCFoundationAPI.cpp')
0 files changed, 0 insertions, 0 deletions