search for: chrec

...s, but haven't yet decided on the > method. Maybe some of you have experience in the area and would like to > advise me something? In the next few days I am going to take a look at > the methods based on chains of recurrences algebra. They seem > particularly interesting because chrecs are already implemented in the > scalar evolution pass. Yes, I'd strongly suggest implementing one of the approaches based on the chrec analysis we have in the scev pass. -Chris -- http://nondot.org/sabre/ http://llvm.org/

...ntly studying some papers, but haven't yet decided on the method. Maybe some of you have experience in the area and would like to advise me something? In the next few days I am going to take a look at the methods based on chains of recurrences algebra. They seem particularly interesting because chrecs are already implemented in the scalar evolution pass. Given the limited time I have for the project, I don't know how precise (and buggy;)) my implementation will be. However, if it appears to be usable, I'll be happy to contribute. --Wojtek

...;t yet decided on the > > method. Maybe some of you have experience in the area and would like to > > advise me something? In the next few days I am going to take a look at > > the methods based on chains of recurrences algebra. They seem > > particularly interesting because chrecs are already implemented in the > > scalar evolution pass. > > Yes, I'd strongly suggest implementing one of the approaches based on the > chrec analysis we have in the scev pass. > Yup, just get the array accesses under scev form, and set a constraint system from these. Onc...

On Nov 29, 2007, at 11:11 AM, Wojciech Matyjewicz wrote: > As you have noticed, loops aren't represented directly in the LLVM IR. > However, there are analysis passes which may be helpful to > "reconstruct" > them. For example: LoopInfo pass detects natural loops (as sets of > basic > blocks) and ScalarEvolution pass finds loop induction variables (and >

>> Yes, I'd strongly suggest implementing one of the approaches based >> on the >> chrec analysis we have in the scev pass. >> > > Yup, just get the array accesses under scev form, and set a constraint > system from these. Once you set up the constraint systems for the > dependence distance vectors, you're almost done. You can look at how > this is set up in...

...s -Wold-style-definition -DHAVE_CONFIG_H -DENABLE_LLVM -D__STDC_LIMIT_MACROS -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I../../gcc/../libcpp/include -I/home/ahs3/tmp/llvm-1.7/llvm/include ../../gcc/tree-nomudflap.c -o tree-nomudflap.o rm -rf libbackend.a ar rc libbackend.a tree-chrec.o tree-scalar-evolution.o tree-data-ref.o tree-cfg.o tree-dfa.o tree-eh.o tree-ssa.o tree-optimize.o tree-gimple.o gimplify.o tree-pretty-print.o tree-into-ssa.o tree-outof-ssa.o tree-ssa-ccp.o tree-vn.o tree-ssa-dce.o tree-ssa-copy.o tree-nrv.o tree-ssa-copyrename.o tree-ssa-pre.o tree-ssa-live.o...

.../sched-ebb.o differs ./sched-rgn.o differs ./sched-vis.o differs ./simplify-rtx.o differs ./sreal.o differs ./stmt.o differs ./stor-layout.o differs ./targhooks.o differs ./timevar.o differs ./tlink.o differs ./toplev.o differs ./tracer.o differs ./tree-browser.o differs ./tree-cfg.o differs ./tree-chrec.o differs ./tree-complex.o differs ./tree-data-ref.o differs ./tree-dfa.o differs ./tree-dump.o differs ./tree-eh.o differs ./tree-gimple.o differs ./tree-if-conv.o differs ./tree-inline.o differs ./tree-into-ssa.o differs ./tree-iterator.o differs ./tree-loop-linear.o differs ./tree-mudflap.o diff...

...fers > ./simplify-rtx.o differs > ./sreal.o differs > ./stmt.o differs > ./stor-layout.o differs > ./targhooks.o differs > ./timevar.o differs > ./tlink.o differs > ./toplev.o differs > ./tracer.o differs > ./tree-browser.o differs > ./tree-cfg.o differs > ./tree-chrec.o differs > ./tree-complex.o differs > ./tree-data-ref.o differs > ./tree-dfa.o differs > ./tree-dump.o differs > ./tree-eh.o differs > ./tree-gimple.o differs > ./tree-if-conv.o differs > ./tree-inline.o differs > ./tree-into-ssa.o differs > ./tree-iterator.o differs...