| Issue 15: | Lattice comparison and join issues | |
| Back to list |
- AliasAwareTupleLE's comparison and join don't match up: what to do with locations present in one but not the other LE? - Make sure that DisjunctiveLE's treat false and true as bottom and top, respectively, and that joining and error reporting work that way. - Make sure transfer function transitions to true upon failures (to preserve monotonicity); prevent error reporting all over the place in this case. Should transition to false when "void" is added to context.
Sep 28, 2008
Project Member
#1
kevin.bi...@gmail.com
Status:
Started
Sep 29, 2008
First bullet addressed in r85. Processing assumes that all locations that *should* have an entry in the tuple *do* have an entry. Default field locations are known to violate that assumption. Nonetheless, regression tests pass. |