[PATCH] D123961: [clang][dataflow] Do not crash on missing `Value` for struct-typed variable init.
Stanislav Gatev via Phabricator via cfe-commits
cfe-commits at lists.llvm.org
Tue Apr 19 09:21:16 PDT 2022
sgatev accepted this revision.
sgatev added inline comments.
Comment at: clang/lib/Analysis/FlowSensitive/Transfer.cpp:184-186
- // FIXME: The initializer expression must always be assigned a value.
- // Replace this with an assert when we have sufficient coverage of
- // language features.
> ymandel wrote:
> > sgatev wrote:
> > > The patch makes sense to me in the current state, but it's unclear why is this not something that we'd like to do in the long term.
> > Because of uninterpreted fields. If we consider those a temporary fix, then I agree about the long term. I'd thought those were here to stay. That said, if we find a way to either interperet fields lazily or only interpret those needed in the current function scope, we may be able to avoid uninterpreted expressions.
> > This also begs the question as to why we insist on initializing the variable. Arguably, if the expresssion is uninterpreted, so should be the variable. So, we should at least explain why we're distinguishing. Thoughts on my adding a comment to that effect?
> >Because of uninterpreted fields.
> Could you elaborate on this? Do you mean fields being uninterpreted due to hitting a depth limit or being recursive? Or is this something else?
Not initializing the variable in such cases also makes sense to me. I'd very much appreciate a comment. I suggest also keeping the FIXME as interpreting fields lazily (and thus relying that all fields that are accessed are initialized) is still an option.
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
More information about the cfe-commits