This is surely a simple question, but it appears that PostDominatorTree does not provide an interface to get at post dominator data. Also, it is not a concrete subclass of DominatorTree, as is presented in the doxygen page and the commented source. Any way to get post-dom data without hacking it into PostDominatorTree?
Is our post-dom pass solid? I thought it's fair expensive so we avoid using it. Evan Sent from my iPhone On May 29, 2009, at 6:14 PM, mgill404 at ucla.edu wrote:> This is surely a simple question, but it appears that > PostDominatorTree does not provide an interface to get at post > dominator data. Also, it is not a concrete subclass of DominatorTree, > as is presented in the doxygen page and the commented source. Any way > to get post-dom data without hacking it into PostDominatorTree? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On Sat, May 30, 2009 at 3:54 PM, Evan Cheng<evan.cheng at apple.com> wrote:> Is our post-dom pass solid? I thought it's fair expensive so we avoid > using it.Our "post-dom pass" is just the dom pass with a boolean set the other way. I don't see how it could be significantly more expensive. I don't think any in-tree passes use it, though. -Eli
Possibly Parallel Threads
- [LLVMdev] Post-dominator data.
- [GSOC 2018] Implement a single updater class for Dominators
- [GSOC 2018] Implement a single updater class for Dominators
- [GSOC 2018] Implement a single updater class for Dominators
- [GSOC 2018] Implement a single updater class for Dominators