If we have several regions which cover the same code area, we should restore
the combined value for that region when return from a nested region.
This patch achieves that goal by combining regions before calling buildSegments.
Differential D18610
[Coverage] Restore the correct count value after processing a nested region in case of combined regions. ikudrin on Mar 30 2016, 11:25 AM. Authored by
Details If we have several regions which cover the same code area, we should restore This patch achieves that goal by combining regions before calling buildSegments.
Diff Detail Event TimelineComment Actions Thanks for the patch. + 1 to Justin's comments.
Comment Actions I think a better fix is to change the active region stack into a stack of entry segments. The resulting code will be more readable.
Comment Actions Thanks a lot for the comments! Please review the new version of the code.
Comment Actions Is it possible to combine identical regions (covering same area) before calling buildSegments? I think the resulting code would be a lot more readable. Comment Actions
Comment Actions
Comment Actions
Please note that I've tried to make the behavior of the new code as close to the original as possible, apart from changes required for fix the described issue. More changes are coming, which will also change this block of code, so it's anyway not the final variant. See D18831. |
This seems like a dead function now.