tree 7e563fdecf5d106267b9e247e6d7de0c17646e10
parent 4d48b5c1d58c381e6e0c719701ef433b530e0e1a
author Jordan Rose <jordan_rose@apple.com> 1341611996 +0000
committer Jordan Rose <jordan_rose@apple.com> 1341611996 +0000

[analyzer] Be careful about LazyCompoundVals, which may be for the first field.

We use LazyCompoundVals to avoid copying the contents of structs and arrays
around in the store, and when we need to pass a struct around that already
has a LazyCompoundVal we just use the original one. However, it's possible
that the first field of a struct may have a LazyCompoundVal of its own, and
we currently can't distinguish a LazyCompoundVal for the first element of a
struct from a LazyCompoundVal for the entire struct. In this case we should
just drop the optimization and make a new LazyCompoundVal that encompasses
the old one.

PR13264 / <rdar://problem/11802440>

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@159866 91177308-0d34-0410-b5e6-96231b3b80d8