Chopper builds wrong ModSetMap when dealing with field-sensitive nodes

[jordr]

See https://gist.github.com/jordr/55817398f88255dedfe206dd8337dba1

[jordr]

David points to PSPA's mayDepend to fix this issue:

https://github.com/davidtr1037/chopper-pspa/blob/0d78f18afe72b99caa23ea7f6ba8cb63a1e5e933/lib/Core/Executor.cpp#L5593-L5611

Debugging commit: 4ac124c

STORE: {
	location =   %x.addr = alloca i8*, align 8,
	instruction =   store i8* %x, i8** %x.addr, align 8
	ValueNodeID = 60,
	ptsto = [		61(insensitive), ]
}
objToStoreMap[foo, 61] =   store i8* %x, i8** %x.addr, align 8
STORE: {
	location = @off = global i32 0, align 4,
	instruction =   store i32 %inc, i32* @off, align 4, !dbg !208
	ValueNodeID = 4,
	ptsto = [		5(insensitive), ]
}
objToStoreMap[foo, 5] =   store i32 %inc, i32* @off, align 4, !dbg !208
STORE: {
	location =   %arrayidx1 = getelementptr inbounds i8* %3, i64 0, !dbg !208,
	instruction =   store i8 %2, i8* %arrayidx1, align 1, !dbg !208
	ValueNodeID = 71,
	ptsto = [		132(sensitive, FIObjNode = 104), ]
}
...

function = foo
	-modPts: 5	-modPts: 61	-modPts: 132
	-refPts: 1	-refPts: 5	-refPts: 9	-refPts: 79	-refPts: 98	-refPts: 104
modSet of foo, 5 =
	-  store i32 %inc, i32* @off, align 4, !dbg !208

[jordr]

Use field insensitive info to fix the modref/getelementptr bug

[jordr]

Should be fixed by d85e634

[jordr]

This also needs ref-set info. See d85e634

But what happens if the mod-set contains a field-insensitive object, and the ref-set contains a field-sensitive version?