search for: deleteloopfromqueue

...> 3. Running pass 'CDFG exitPass' on basic block '%bb3' >> ./optScript.sh: line 46: 2637 Segmentation fault opt -load >> /home/ryan/llvm/llvm_core/llvm-2.9/Release/lib/LLVMEXITCDFG.so -exitPass >> $1.bc -o ${1}.bc >> >> If I remove the "deleteLoopFromQueue" function call, it goes over all the >> loops (supposedly extracting them) and then segFaults. >> >> How should I properly use this function? >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail...

...Pass Manager' on function '@fix_fft' 3. Running pass 'CDFG exitPass' on basic block '%bb3' ./optScript.sh: line 46: 2637 Segmentation fault opt -load /home/ryan/llvm/llvm_core/llvm-2.9/Release/lib/LLVMEXITCDFG.so -exitPass $1.bc -o ${1}.bc If I remove the "deleteLoopFromQueue" function call, it goes over all the loops (supposedly extracting them) and then segFaults. How should I properly use this function? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120112/3dd964f7/attac...

...fix_fft' >> 3. Running pass 'CDFG exitPass' on basic block '%bb3' >> ./optScript.sh: line 46: 2637 Segmentation fault opt -load /home/ryan/llvm/llvm_core/llvm-2.9/Release/lib/LLVMEXITCDFG.so -exitPass $1.bc -o ${1}.bc >> >> If I remove the "deleteLoopFromQueue" function call, it goes over all the loops (supposedly extracting them) and then segFaults. >> >> How should I properly use this function? >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc...

...'@fix_fft' > 3. Running pass 'CDFG exitPass' on basic block '%bb3' > ./optScript.sh: line 46: 2637 Segmentation fault opt -load > /home/ryan/llvm/llvm_core/llvm-2.9/Release/lib/LLVMEXITCDFG.so -exitPass > $1.bc -o ${1}.bc > > If I remove the "deleteLoopFromQueue" function call, it goes over all the > loops (supposedly extracting them) and then segFaults. > > How should I properly use this function? > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/2012...

...[with BlockT = llvm::BasicBlock, LoopT = llvm::Loop]: Assertion `HasInsideLoopPreds && "Loop block has no in-loop predecessors!"' failed. > > Does this mean I should keep it still a loop after my pass? If so, how could I bypass it? You might need to call LPPassManager::deleteLoopFromQueue(). -Andy > -- > Thank you && Best Regards, > > Zhiyuan Yang > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev ------...

...ful to check everything that's currently disabled when LPM is missing: domtree update, ScalarEvolution update, SimplifyIndvar. If you need any of these things I suggest changing the interface. Maybe it would work to pass in FunctionPass instead of LPM. In the one place we actually need an LPM (deleteLoopFromQueue), we could check FunctionPass's type and cast. Maybe getAsPMDataManager()->getPassManagerType() == PMT_LoopPassManager? -Andy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120605/d1df85f8/attachment...

Hi, I am writing a loop pass to replace the backedge with an edge from latch to exit. Now I just replace the terminator of latch with another BranchInst, and the loop will not be a loop after my pass. However, it turns out a failure of loopverify after executing my pass: opt: ~/llvm/llvm-trunk/include/llvm/Analysis/LoopInfoImpl.h:297: void llvm::LoopBase<N, M>::verifyLoop() const [with

...ock, > LoopT = llvm::Loop]: Assertion `HasInsideLoopPreds && "Loop block has no > in-loop predecessors!"' failed. > > Does this mean I should keep it still a loop after my pass? If so, how > could I bypass it? > > > You might need to call LPPassManager::deleteLoopFromQueue(). > > -Andy > > -- > > *Thank you && Best Regards,* > > *Zhiyuan Yang* > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/l...

I am trying to implement loop unrolling in a context, where lots of constant propagation has taken place. Unrolling an outer loop might make an inner loop have constant bounds, therefore I want to process the loops outside in, i.e. from parent loops to nested loops. Unfortunately the standard loop pass manager performs loop passes inside out, i.e. from nested loops to parent loops, thereby missing

...llvm-obj/lib/Analysis/Release/LoopPass.d"; else /bin/rm "/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis/Release/LoopPass.d.tmp"; exit 1; fi /home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/lib/Analysis/LoopPass.cpp: In member function 'void llvm::LPPassManager::deleteLoopFromQueue(llvm::Loop*)': /home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/lib/Analysis/LoopPass.cpp:100: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <https://support.codesourcery.com/GNUToolchain/> for instructions. /bin/...

...LoopPass.d"; > else /bin/rm > "/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis/Release/LoopPass.d.tmp"; > exit 1; fi > /home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/lib/Analysis/LoopPass.cpp: > In member function 'void > llvm::LPPassManager::deleteLoopFromQueue(llvm::Loop*)': > /home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/lib/Analysis/LoopPass.cpp:100: > internal compiler error: Segmentation fault > Please submit a full bug report, > with preprocessed source if appropriate. > See <https://support.codesourcery.com/GNUToolchain/&gt...

...ng similar, but I'm not sure that's very pretty. Any suggestions? Additionally, after loop unrolling, the following check is made: // Update the loop information for this loop. // If we completely unrolled the loop, remove it from the parent. if (L->getNumBackEdges() == 0) LPM.deleteLoopFromQueue(L); This check probably needs to happen in every unroll pass that use loopUnroll. We could move this check into the loopUnroll function, but that requires passing in the LoopPassManager (LPM) to loopUnroll as well. Is that wanted? Overall, I've really only moved code, so behaviour should be u...

Updated to remove all the loops in the loop-nest from the queue because there no way to remove specific loop(s) from the queue. Deleting loop(s) from queue using deleteLoopFromQueue changes the loop nest.   -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100713/3cfda735/attachment.html> -------------- next part -------------- An embedded and charset-unspecified text was scrub...

...ass 'CDFG exitPass' on basic block '%bb3' >>> ./optScript.sh: line 46: 2637 Segmentation fault opt -load >>> /home/ryan/llvm/llvm_core/llvm-2.9/Release/lib/LLVMEXITCDFG.so -exitPass >>> $1.bc -o ${1}.bc >>> >>> If I remove the "deleteLoopFromQueue" function call, it goes over all >>> the loops (supposedly extracting them) and then segFaults. >>> >>> How should I properly use this function? >>> >> >> > _______________________________________________ > LLVM Developers mailing list >...

Prasanth J wrote: > > Hi all, > with reference to the reply below, I downloaded toolchain from > codesourcery (arm-2009q1-203-arm-none-linux-gnueabi) with gcc 4.3.3... > when i compile llvm+clang with this toolchain i am getting the > following error > > make[4]: Entering directory >

Hello Matthijs, Separating mechanism from policy is a good thing for the LoopUnroll pass. Instead of moving the policy to a subclass though, I think it'd be better to move the mechanism, the unrollLoop function, out to be a standalone utility function, with the LoopInfo object passed in explicitly. FoldBlockIntoPredecessor would also be good to make into a standalone utility function, since

...> > > "/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis/Release/LoopPass.d.tmp"; > > exit 1; fi > > > /home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/lib/Analysis/LoopPass.cpp: > > In member function 'void > > llvm::LPPassManager::deleteLoopFromQueue(llvm::Loop*)': > > > /home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/lib/Analysis/LoopPass.cpp:100: > > internal compiler error: Segmentation fault > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See <https://support.cod...

...Form would be a good addition in any case. > > > Additionally, after loop unrolling, the following check is made: > // Update the loop information for this loop. > // If we completely unrolled the loop, remove it from the parent. > if (L->getNumBackEdges() == 0) > LPM.deleteLoopFromQueue(L); > > This check probably needs to happen in every unroll pass that use > loopUnroll. > We could move this check into the loopUnroll function, but that > requires > passing in the LoopPassManager (LPM) to loopUnroll as well. Is that > wanted? I don't think it's...