search for: scopdetection

...- 0.54% 0x460032 + llvm::StoreInst::~StoreInst() GDB is a useful tool! Thanks for Sebastian's advice! By setting a break point on llvm::TypeFinder::run(llvm::Module const&, bool), I find most of calling cases are issued from the following two callsites: 0xb7c1c5d2 in polly::ScopDetection::isValidMemoryAccess(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const () 0xb7c1d754 in polly::ScopDetection::isValidInstruction(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const () The detailed backtrace of "isValidMemoryAccess" is: #0...

...StoreInst::~StoreInst() > > > GDB is a useful tool! Thanks for Sebastian's advice! > > By setting a break point on llvm::TypeFinder::run(llvm::Module const&, > bool), I find most of calling cases are issued from the following two > callsites: > 0xb7c1c5d2 in polly::ScopDetection::isValidMemoryAccess(llvm::Instruction&, > polly::ScopDetection::DetectionContext&) const () > 0xb7c1d754 in polly::ScopDetection::isValidInstruction(llvm::Instruction&, > polly::ScopDetection::DetectionContext&) const () > > The detailed backtrace of "isValidMem...

...olly-dot" and "polly-dot-only". However, I see all these options are defined as "static" variables in lib/RegisterPasses.cpp. Do you think I should translate these local variables into global variables or should I define another option like "-polly-dot-scop" in ScopDetection.cpp? > >You can define a new option -polly-detect-collect-errors that enables >the error tracking. Adding cl::location to this option allows you to >store the option value externally. You can use this to automatically >set this option, in case in lib/RegisterPasses.cpp in case -poll...

...s is only > called in DEBUG mode with DEBUG macro or in PollyView mode. > > With this patch file, the relative compile-time cost of Polly-detect pass does > not increase even compiling very large size source code. > --- > include/polly/Options.h | 3 ++ > include/polly/ScopDetection.h | 6 +++ > lib/Analysis/ScopDetection.cpp | 93 +++++++++++++++++++++++------------------- > lib/RegisterPasses.cpp | 22 ++++++---- > 4 files changed, 75 insertions(+), 49 deletions(-) > > diff --git a/include/polly/Options.h b/include/polly/Options.h > index 62e0960....

...could do this: > > > > 1) Make ScopInfo & DependenceInfo function passes to avoid the > > RegionPassManager for these Polly analysis parts. [This doesn't > > need to be the first step but it should be done at some point.] > > 2) Create a secondary ScopDetection & ScopInfo that is restricted to > > analyze a single loop. We might just create a dummy region for this > > loop and use the original ScopDetection & ScopInfo. The goal is to > > make (this secondary) ScopDetection & ScopInfo demand driven and > >...

...- 0.54% 0x460032 + llvm::StoreInst::~StoreInst() GDB is a useful tool! Thanks for Sebastian's advice! By setting a break point on llvm::TypeFinder::run(llvm::Module const&, bool), I find most of calling cases are issued from! the following two callsites: 0xb7c1c5d2 in polly::ScopDetection::isValidMemoryAccess(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const () 0xb7c1d754 in polly::ScopDetection::isValidInstruction(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const () The detailed backtrace of "isValidMemoryAccess" is: #0...

...olly-dot" and "polly-dot-only". However, I see all these options are defined as "static" variables in lib/RegisterPasses.cpp. Do you think I should translate these local variables into global variables or should I define another option like "-polly-dot-scop" in ScopDetection.cpp? You can define a new option -polly-detect-collect-errors that enables the error tracking. Adding cl::location to this option allows you to store the option value externally. You can use this to automatically set this option, in case in lib/RegisterPasses.cpp in case -polly-show, -polly-show...

...e proposal too, though it is not the only way we could do this: 1) Make ScopInfo & DependenceInfo function passes to avoid the RegionPassManager for these Polly analysis parts. [This doesn't need to be the first step but it should be done at some point.] 2) Create a secondary ScopDetection & ScopInfo that is restricted to analyze a single loop. We might just create a dummy region for this loop and use the original ScopDetection & ScopInfo. The goal is to make (this secondary) ScopDetection & ScopInfo demand driven and non-dependent on the RegionInfo an...

...not the only way we > could do this: > > 1) Make ScopInfo & DependenceInfo function passes to avoid the > RegionPassManager for these Polly analysis parts. [This doesn't > need to be the first step but it should be done at some point.] > 2) Create a secondary ScopDetection & ScopInfo that is restricted to > analyze a single loop. We might just create a dummy region for this > loop and use the original ScopDetection & ScopInfo. The goal is to > make (this secondary) ScopDetection & ScopInfo demand driven and > non-dependent...

...>> >> GDB is a useful tool! Thanks for Sebastian's advice! >> >> By setting a break point on llvm::TypeFinder::run(llvm::Module const&, >> bool), I find most of calling cases are issued from the following two >> callsites: >> 0xb7c1c5d2 in polly::ScopDetection::isValidMemoryAccess(llvm::Instruction&, >> polly::ScopDetection::DetectionContext&) const () >> 0xb7c1d754 in polly::ScopDetection::isValidInstruction(llvm::Instruction&, >> polly::ScopDetection::DetectionContext&) const () >> >> The detailed backtrace...

...> > > > 1) Make ScopInfo & DependenceInfo function passes to avoid the > > > RegionPassManager for these Polly analysis parts. [This doesn't > > > need to be the first step but it should be done at some point.] > > > 2) Create a secondary ScopDetection & ScopInfo that is restricted to > > > analyze a single loop. We might just create a dummy region for > this > > > loop and use the original ScopDetection & ScopInfo. The goal is to > > > make (this secondary) ScopDetection & ScopInfo demand...

...t; > 1) Make ScopInfo & DependenceInfo function passes to avoid the >> > > RegionPassManager for these Polly analysis parts. [This doesn't >> > > need to be the first step but it should be done at some point.] >> > > 2) Create a secondary ScopDetection & ScopInfo that is restricted to >> > > analyze a single loop. We might just create a dummy region for >> this >> > > loop and use the original ScopDetection & ScopInfo. The goal is >> to >> > > make (this secondary) ScopDetecti...

I have modified the code as follows; now i am using both scopdetection and scopinformation before dependency check but i think link is missing... virtual bool runOnFunction(Function &F) { std::unique_ptr<ScopInfo> Result; std::unique_ptr<ScopDetection> Result2; //polly::ScopDetection pl; auto &LI = getAnalysis<LoopInfoWrapperPass>(...

...i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" > > target triple = "x86_64-unknown-linux-gnu" > > > > If I remove that XFAIL the testcase is ICEing on my ARM laptop with: > > opt: ../tools/polly/lib/Analysis/ScopDetection.cpp:353: bool polly::ScopDetection::isValidInstruction(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const: Assertion `!Context.Verifying && "IndVar"' failed. > This was with ISL as of this commit: commit 02b2b6f2298d6beca919692219a287986e984347 Au...

...mply remove the string buffer operation. This patch file can significantly reduce compile-time overhead when compiling big source code. For example, for oggen*8.ll, the compile time is reduced from 40.5261 ( 51.2%) to 5.8813s (15.9%) with this patch file. On top of your patch, I have removed from ScopDetection.cpp all printing of LLVM values, like this: - INVALID(AffFunc, "Non affine access function: " << *AccessFunction); + INVALID(AffFunc, "Non affine access function: "); there are a good dozen or so of these pretty printing. With these changes the compile time spent...

...ut-of-tree context. If you build your pass as a loadable library, you're free to link against Polly and include its headers. Cheers, Philip 2018-01-28 18:20 GMT+01:00 hameeza ahmed via llvm-dev < llvm-dev at lists.llvm.org>: > I have modified the code as follows; now i am using both scopdetection and > scopinformation before dependency check but i think link is missing... > > virtual bool runOnFunction(Function &F) > { > > std::unique_ptr<ScopInfo> Result; > std::unique_ptr<ScopDetection> Result2; > //polly::ScopDetection pl; > > auto &a...

...8:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" >>>> target triple = "x86_64-unknown-linux-gnu" >>>> >>> >>> If I remove that XFAIL the testcase is ICEing on my ARM laptop with: >>> >>> opt: ../tools/polly/lib/Analysis/ScopDetection.cpp:353: bool polly::ScopDetection::isValidInstruction(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const: Assertion `!Context.Verifying && "IndVar"' failed. >>> >> >> This was with ISL as of this commit: >> >> commit 02...

...hhb <etherzhhb at gmail.com>: > Hi, > > 2011/4/8 Vlad Krylov <krvladislav at gmail.com>: >> Hi. >> >> I see that to detect scops firstly we search for regions in CFG ( by >> RegionInfo ) and then select regions that answer some requirements ( >> in ScopDetection ). Because only affine expressions in conditions and >> bounds are permissible, we trying to get scalar expressions into >> affine form by AffineSCEVIterator. At present there plugs for scev >> types Truncate, ZeroExtend, SignExtend, UDivExpr, UMaxExpr , SMaxExpr. >> Also th...

...:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" > target triple = "x86_64-unknown-linux-gnu" > If I remove that XFAIL the testcase is ICEing on my ARM laptop with: opt: ../tools/polly/lib/Analysis/ScopDetection.cpp:353: bool polly::ScopDetection::isValidInstruction(llvm::Instruction&, polly::ScopDetection::DetectionContext&) const: Assertion `!Context.Verifying && "IndVar"' failed. Sebastian -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The...

Hello, I need to analyze dependencies in my llvm ir by using polly. i created a new pass called mypass there i added polly dependency analysis pass but when i execute this pass in gdb i get no data. Why is that so? My code is follows; namespace { struct mypass : public FunctionPass { static char ID; mypass() : FunctionPass(ID) { } virtual bool runOnFunction(Function &F) {