summaryrefslogtreecommitdiff
path: root/polly
diff options
context:
space:
mode:
authorJakub Kuderski <kubakuderski@gmail.com>2018-07-28 00:54:07 +0000
committerJakub Kuderski <kubakuderski@gmail.com>2018-07-28 00:54:07 +0000
commitc2f29ed03a1b5f0a90d60ee9f1113577b9835881 (patch)
treed10b95953415b1893abe66c15a23580b25030c9f /polly
parent5e731eed6fca4c10f9518bc28a7935c4d1d031aa (diff)
[Dominators] Make applyUpdate's documentation less confusing [NFC]
Summary: It was pointed out by @chandlerc that it's not clear whether both applyUpdates and insert/deleteEdge can be used to perform multiple updates. IMO, the confusing part was that the comment above applyUpdates made a comparison of expected update time between calling it and calling insert/deleteEdge multiple times. It's generally not possible to safely call insert/deleteEdge multiple times, which documentation for each of the 3 functions warns about, so the whole comparison makes very little sense. On top of that, the comment is already lengthy, so I think it's best to just get rid of this comparison. Reviewers: chandlerc, asbirlea, NutshellySima, grosser Reviewed By: chandlerc Subscribers: llvm-commits, chandlerc Differential Revision: https://reviews.llvm.org/D49944
Diffstat (limited to 'polly')
0 files changed, 0 insertions, 0 deletions