summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/Scalar/SCCP.cpp
diff options
context:
space:
mode:
authorSanjoy Das <sanjoy@playingwithpointers.com>2016-12-11 20:07:15 +0000
committerSanjoy Das <sanjoy@playingwithpointers.com>2016-12-11 20:07:15 +0000
commit3336f681e3f548e082d363b848edaeb3e0fcb644 (patch)
tree36736acde3a80e22994651d343fe2d3435179107 /llvm/lib/Transforms/Scalar/SCCP.cpp
parent81ed3499cdf61dcf3cfb426de24f4f406bd04b0f (diff)
downloadbcm5719-llvm-3336f681e3f548e082d363b848edaeb3e0fcb644.tar.gz
bcm5719-llvm-3336f681e3f548e082d363b848edaeb3e0fcb644.zip
[Verifier] Add verification for TBAA metadata
Summary: This change adds some verification in the IR verifier around struct path TBAA metadata. Other than some basic sanity checks (e.g. we get constant integers where we expect constant integers), this checks: - That by the time an struct access tuple `(base-type, offset)` is "reduced" to a scalar base type, the offset is `0`. For instance, in C++ you can't start from, say `("struct-a", 16)`, and end up with `("int", 4)` -- by the time the base type is `"int"`, the offset better be zero. In particular, a variant of this invariant is needed for `llvm::getMostGenericTBAA` to be correct. - That there are no cycles in a struct path. - That struct type nodes have their offsets listed in an ascending order. - That when generating the struct access path, you eventually reach the access type listed in the tbaa tag node. Reviewers: dexonsmith, chandlerc, reames, mehdi_amini, manmanren Subscribers: mcrosier, llvm-commits Differential Revision: https://reviews.llvm.org/D26438 llvm-svn: 289402
Diffstat (limited to 'llvm/lib/Transforms/Scalar/SCCP.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud