Displaying 6 results from an estimated 6 matches for "immediatedominators".
2005 May 16
1
[LLVMdev] Invalidating an analysis pass
Hi,
How can I rerun an analysis pass in the middle of a function pass? In
particular, my dominator set needs to be recomputed.
It looks like I can manually edit the dominator set with
getAnalysisToUpdate. If I could rerun the dominator set pass to get
this info automatically, it would save me some time.
Thanks.
2006 Jul 05
0
[LLVMdev] Critical edges
...nch instructions)?
Thanks a lot,
Fernando
Code ---------------------------------------------------------------
void CriticalEdgeRemoval_Fer::getAnalysisUsage
(AnalysisUsage & AU) const {
AU.addPreserved<ETForest>();
AU.addPreserved<DominatorSet>();
AU.addPreserved<ImmediateDominators>();
AU.addPreserved<DominatorTree>();
AU.addPreserved<DominanceFrontier>();
AU.addPreserved<LoopInfo>();
AU.addPreservedID(LoopSimplifyID);
}
bool CriticalEdgeRemoval_Fer::runOnMachineFunction
(MachineFunction & mf) {
std::vector<MachineBasicBlock *...
2006 Jul 04
2
[LLVMdev] Critical edges
On Tue, 4 Jul 2006, Fernando Magno Quintao Pereira wrote:
> However, it does not remove all the critical edges. I am getting a very
> weird dataflow graph (even without the Break Critical edges pass). The
> dataflow generated by MachineFunction::dump() for the program below is
> given here:
> http://compilers.cs.ucla.edu/fernando/projects/soc/images/loop_no_crit2.pdf
...
> The
2007 May 23
0
LLVM 2.0 Release
LLVM 2.0 is done! Download it here: http://llvm.org/releases/ or view
the release notes: http://llvm.org/releases/2.0/docs/ReleaseNotes.html
LLVM 2.0 is a great release in many ways. It includes a wide range of new
features, new optimizations, better codegen, and new targets. We were
also able to signficantly revise several core aspects of the LLVM IR and
design (such as the type system
2007 May 14
3
[LLVMdev] llvm 2.0 release announcement [draft]
Hi Everyone,
It is getting to be that time again. I've scoured llvm-commits and
collected a list of some of the major features we've developed since
the last status update (from Feb 21). Please take a look and send me
(off list) additions, feedback, corrections, etc. As usual, if I
missed something, it's probably because there is such a huge amount
of stuff happening,
2006 May 09
1
[LLVMdev] Memory leaks in LLVM
...F0: operator new(unsigned) (vg_replace_malloc.c:164)
==10132== by 0x8499B7E: llvm::ETNode::setFather(llvm::ETNode*) (
Dominators.cpp:661)
==10132== by 0x849A2CE:
llvm::ETForest::getNodeForBlock(llvm::BasicBlock*) ( Dominators.cpp:848)
==10132== by 0x849A467:
llvm::ETForest::calculate(llvm::ImmediateDominators const&) (Dominators.cpp
:865)
==10132== by 0x85010FD: llvm::ETForest::runOnFunction(llvm::Function&) (
Dominators.h :506)
==10132== by 0x850FD3E:
llvm::FunctionPassManagerT::runPass(llvm::FunctionPass*, llvm::Function*) (
PassManagerT.h:795)
==10132== by 0x85115E9:
llvm::PassManage...