search for: smaxexpr

...e 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 there are no support for wrap flags NUW, NSW, NW. It can be > unsafe if we doesn't provide this information in polly IR. Yes, if AffineSCEVIterator can iterate Truncate, ZeroExtend and SignExtend correctly, polly can accept much more Scops. > > So I will mainly improve Affin...

...>> 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 there are no support for wrap flags NUW, NSW, NW. It can be >> unsafe if we doesn't provide this information in polly IR. > Yes, if AffineSCEVIterator can iterate Truncate, ZeroExtend and > SignExtend correctly, polly can accept much more Scops. >> >> So I...

...ions 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 there are no support for wrap flags NUW, NSW, NW. It can be unsafe if we doesn't provide this information in polly IR. So I will mainly improve AffineSCEVIterator. Now I should to show test cases indicating that - loops with above-listed types expressions cannot be converted to the polyh...

...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 there are no support for wrap flags NUW, NSW, NW. It can be >>> unsafe if we doesn't provide this information in polly IR. >> Yes, if AffineSCEVIterator can iterate Truncate, ZeroExtend and >> SignExtend correctly, polly can accept much more Scops. >&g...

...on ). 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 there are no support for wrap flags NUW, NSW, NW. It can be >>>> unsafe if we doesn't provide this information in polly IR. >>> >>> Yes, if AffineSCEVIterator can iterate Truncate, ZeroExtend and >>> SignExtend correctly, polly can a...

...>> 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 there are no support for wrap flags NUW, NSW, NW. It can be >> unsafe if we doesn't provide this information in polly IR. > Yes, if AffineSCEVIterator can iterate Truncate, ZeroExtend and > SignExtend correctly, polly can accept much more Scops. >> >> So I...

On 04/04/2011 12:23 AM, Vlad Krylov wrote: > > Hi. Hi Vlad, first of all it seems the conflict with raghesh was already solved. Nice. Regarding your draft. It looks like a reasonable first version, but it obviously needs to be extended for the final application. I would also recommend to install Polly and try to find the first test cases that cannot be handled. Some comments to your

Hi. My plan would be: 1w Study sources of Polly and LLVM docs relating to analysis. 2w Create tests which demonstrate problems with NSW/NUW 3-4w Fix the handling of wrap overflows. 5w Complete middle term paperwork. 6w Create tests for each of cases which are not currently optimized (e.g. have min/max, sext/zext, trunc or unsigned comparisons in the loop bounds or memory accesses). 7w Learn how

On Tue, Jan 24, 2017 at 1:20 PM, Sanjay Patel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > I started looking at the log files that you attached, and I'm confused. > The code that is supposedly causing the perf regression is created by the > loop vectorizer, right? Except the bad code is not in the "vector.body", so > is there something peculiar about