Test cases to be written for which verification is to be done. @manasthakur sir please provide us some test cases you can think of whenever you are free.

For Store statements of type a.f = b, changes to be made are:
es(a) to be copied into es(b) and all objects reachable from b.

For Load statements of type b = a.f, changes to be made are:

1. If a.f already exists:
   b -> [assimilate all objects pointed to by a.f]. Should a new object be created here?
2. if a.f doesn't already exist: (can a be a field variable in such a case?)
   a.f -> [new object]
b -> [same new object]
es(same new object) = es(a).f

Looks like the BCIs for array allocations are being picked up from the next statement (found in moldyn/md.runiters).

Plan: Check this with a small program involving different kinds of array allocations.

Solution(s): Perhaps get the BCI of the predecessor from the control-flow graph? Else subtract correct offset based on the kind of array-alloc instruction.

Should new array statements be tracked for their escape status or shall we just discard them as objects that escape?

Store statements must have weak updates. The strong and weak updates carry meaning only for store statements. All other statements must have normal updates.

Ensure all methods use the ObjectFactory to create a new ObjectNode. The responsibility to figure out ObjectType lies on the caller.

Insert comments for each method describing the case that it is meant to cover.