search for: detectioncontext

...ol! 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 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&, bool) () #1 0x08f76e...

...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 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&...

...gt; 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 0x0907b780 in llvm::TypeFinder::run(llv...

...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 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&, bool) () #1 0x08f76e...

...et 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 Author: Sven Verdoolaege <skimo at kotnet.org> Date: Tue Apr 9 17:37:46 2013 +0200 When updating ISL to master...

...nux-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 >> Author: Sven Verdoolaege <skimo at kotnet.org> >> Date:...

...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 Linux Foundation

...gt;>>>> >>>>> 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 >>>> Author: Sven Verdoolae...

...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 > Author: Sven Verdoolaege <skimo at kotnet.org> > Date: Tue Apr 9 17:37:46 2013...

...t;>>> >>>> >>>> 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 >>> Author: Sven Verdoolaege <skimo at kotnet.o...

...t;>>>>> 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 02b2b6f2298d6beca919692219a287986e9...

The attached patch eliminates http://llvm.org/bugs/show_bug.cgi?id=15817 by removing the remaining "; XFAIL:*" added in http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130415/171812.html. The Isl/CodeGen/scevcodegen-1.ll testcase in polly appears as an XPASS in current llvm/polly 3.3 and trunk svn for both x86_64-apple-darwin* and x86_64 Fedora 15 when built against isl

...gt;> >>>>>> 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 >>>>&gt...

...ll instruction is valid, false otherwise. > static bool isValidCallInst(CallInst &CI); > > + /// @brief Report invalid alias. > + /// > + /// @param AS The alias set. > + /// @param Context The context of scop detection. > + void reportInvalidAlias(AliasSet &AS, DetectionContext &Context) const; Nice. > diff --git a/lib/Analysis/ScopDetection.cpp b/lib/Analysis/ScopDetection.cpp > index 9b2a9a8..4f33f6c 100644 > --- a/lib/Analysis/ScopDetection.cpp > +++ b/lib/Analysis/ScopDetection.cpp > @@ -108,11 +108,13 @@ STATISTIC(ValidRegion, "Number of regi...

...>>>> 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 02b2b6f2298d6beca919...

Hi Tobias, I have attached a patch file to optimize string operations in Polly-Detect pass. In this patch file, I put most of long string operations in the condition variable of "PollyViewMode" or in the DEBUG mode. Bests, Star Tan At 2013-07-22 22:27:48,"Tobias Grosser" <tobias at grosser.es> wrote: >On 07/22/2013 01:46 AM, Star Tan wrote: >> At

On 07/22/2013 01:46 AM, Star Tan wrote: > At 2013-07-22 12:16:53,"Tobias Grosser" <tobias at grosser.es> wrote: >> I propose two more patches: >> >> 1) Transform the INVALID macro into function calls, that format >> the text and that set LastFailure. > Translating the INVALID macro into function calls would complicate the operations for