This test shows that DTU with Eager strategy fails to update the DomTree properly while Lazy strategy works OK.
Details
Details
- Reviewers
- None
Diff Detail
Diff Detail
Event Timeline
Comment Actions
@mkazantsev Can you replace insert/deleteEdge with a bundle of updates using DTU.applyUpdates? Just eyeballing the code, it's very likely you are misusing the API by not respecting the contract of insertEdge/deleteEdge -- like Alina explained in the other thread.
I don't have any recent builds of LLVM ready and it would help me of you checked it, as a quick sanity check.
Comment Actions
In short, when you do an update you have to inform about all of the changes that happened since the last update/construction at once. When you do that separately, Domtree gets confused because it's out of sync with the CFG.