search for: polyhedralinfo

...ect. Based upon this discussion, I am planning to cover the following items in the first month of this GSoC. 1: Decouple ScopInfo object from pass and create two passes. One region pass to preserve compatibility with existing Polly transformation passes, other will be a function pass to be used by PolyhedralInfo pass as mentioned below. 2: Decouple DependenceInfo object from pass and create two passes. Same as above. 3: Create the interface PolyhedralInfo, which will extract Memory Access wise dependence information from Polly and provide few simple interfaces like isParallel(), isVectorizable(), tripCou...

In the design the LLVM passes always directly communicate with PolyhedralInfo, this requires Polly tightly integrate in to LLVM. If we do not want a tight integration, we can do the following: 1. Introduce an abstract memory dependency query interface, like AliasAnalysis 2. I remember LLVM had already have dependency analysis, this can be the default implementation of the m...

...-[uses]--| Dependences | | | | | |-----[queries]--| |-----[uses]--| |---[uses]---| | | V V | New Pass/Interface: |----------- PolyhedralInfo --[queries]--| A | | [non-polyhedral queries] |...

...t if Polly is not compiled with LLVM tools. Regards, Utpal Bora Ph.D. Scholar +917032002001 Computer Science & Engineering IIT Hyderabad On Fri, Mar 25, 2016 at 7:53 AM, Hongbin Zheng <etherzhhb at gmail.com> wrote: > In the design the LLVM passes always directly communicate with PolyhedralInfo, > this requires Polly tightly integrate in to LLVM. > > If we do not want a tight integration, we can do the following: > 1. Introduce an abstract memory dependency query interface, like > AliasAnalysis > 2. I remember LLVM had already have dependency analysis, this can be the &g...

Hi, I am Adil Arun Dangui, a 3rd year B.Tech student at IIT Hyderabad with a CGPA of 9.17. I am interested in Compilers, Compiler Optimizations and excited about LLVM and Polly. I have some familiarity of LLVM structure as we studied it in the Compiler Engineering course at IITH. Here

On Fri, Oct 13, 2017 at 5:13 PM, Michael Kruse via llvm-dev < llvm-dev at lists.llvm.org> wrote: > 2017-10-14 1:29 GMT+02:00 Saito, Hideki via llvm-dev < > llvm-dev at lists.llvm.org>: > > I'm also sorry that I'm not commenting on the main part of your RFC in > this reply. I just want to focus on > > one thing here. > > > >

...profit from the knowledge contained in a "Scop" object. 4) Start an API that translates (simple) queries from the LLVM passes to lookups in a Scop. The LLVM pass should never "see" the Scop object or anything related for that matter. It will only require a "PolyhedralInfo" pass and query it. 5) Use the above API to augment the information available at the points identified in 3), but only if the available information is not sufficient to apply the intended transformation. 6) Evaluate the impact on compile and runtime for each pass that was au...

...esses constructing polyhedral dependences for all the SCoP objects of a function. 3. These patches are currently under review and I am incorporating changes as suggested by the Polly community. 4. Implemented first version of an interface to Polly's analysis passes- PolyhedralInfo pass (D21486 <http://reviews.llvm.org/D21486>). Implemented isParallel(Loop *) interface to check parallelism of a loop. Pending Work: 1. Complete the interface - PolyhederalInfo pass. Currently I am working on providing more interfaces to check whether a loop is vectorizable...

...ledge contained in a "Scop" object. > 4) Start an API that translates (simple) queries from the LLVM passes > to lookups in a Scop. The LLVM pass should never "see" the Scop > object or anything related for that matter. It will only require a > "PolyhedralInfo" pass and query it. > 5) Use the above API to augment the information available at the > points identified in 3), but only if the available information is > not sufficient to apply the intended transformation. > 6) Evaluate the impact on compile and runtime for each p...

...perations, which worked around lack of support in ScalarEvolution, is being replaced thanks to improvements being contributed to ScalarEvolution itself (see D34598). Polly’s core delinearization routines have long been a part of LLVM itself. * PolyhedralInfo, which exposes a subset of Polly’s loop analysis for use by other clients, is now available. * Polly is now part of the LLVM release process and is being included with LLVM by various packagers (e.g., Debian). I believe that the LLVM community w...

...being > > replaced thanks to improvements being contributed to ScalarEvolution > > itself (see D34598). Polly’s core delinearization routines have long > > been a part of LLVM itself. > > > > * > > > > PolyhedralInfo, which exposes a subset of Polly’s loop analysis for > > use by other clients, is now available. > > > > * > > > > Polly is now part of the LLVM release process and is being included > > with LLVM by various packagers...

...which worked around lack of support in ScalarEvolution, is being >> replaced thanks to improvements being contributed to >> ScalarEvolution itself (see D34598). Polly’s core delinearization >> routines have long been a part of LLVM itself. >> * >> PolyhedralInfo, which exposes a subset of Polly’s loop analysis >> for use by other clients, is now available. >> * >> Polly is now part of the LLVM release process and is being >> included with LLVM by various packagers (e.g., Debian). >> >> >> I believe tha...

...ling signed division/remainder operations, which worked around lack of support in ScalarEvolution, is being replaced thanks to improvements being contributed to ScalarEvolution itself (see D34598). Polly’s core delinearization routines have long been a part of LLVM itself. * PolyhedralInfo, which exposes a subset of Polly’s loop analysis for use by other clients, is now available. * Polly is now part of the LLVM release process and is being included with LLVM by various packagers (e.g., Debian). I believe that the LLVM community would benefit from beginning the pro...

...ing > signed division/remainder operations, which worked around lack of support > in ScalarEvolution, is being replaced thanks to improvements being > contributed to ScalarEvolution itself (see D34598). Polly’s core > delinearization routines have long been a part of LLVM itself. - > PolyhedralInfo, which exposes a subset of Polly’s loop analysis for use by > other clients, is now available. - Polly is now part of the LLVM release > process and is being included with LLVM by various packagers (e.g., > Debian). I believe that the LLVM community would benefit from beginning the > pr...

...ethod of handling signed division/remainder operations, which worked around lack of support in ScalarEvolution, is being replaced thanks to improvements being contributed to ScalarEvolution itself (see D34598). Polly’s core delinearization routines have long been a part of LLVM itself. >>> PolyhedralInfo, which exposes a subset of Polly’s loop analysis for use by other clients, is now available. >>> Polly is now part of the LLVM release process and is being included with LLVM by various packagers (e.g., Debian). >>> >>> I believe that the LLVM community would benefit fro...

...und lack of support in ScalarEvolution, is being > > replaced thanks to improvements being contributed to ScalarEvolution > > itself (see D34598). Polly’s core delinearization routines have long > > been a part of LLVM itself. > > > > * > > > > PolyhedralInfo, which exposes a subset of Polly’s loop analysis for > > use by other clients, is now available. > > > > * > > > > Polly is now part of the LLVM release process and is being included > > with LLVM by various packagers (e.g., Debian). > > > >...

...rations, > which worked around lack of support in ScalarEvolution, is being > replaced thanks to improvements being contributed to ScalarEvolution > itself (see D34598). Polly’s core delinearization routines have long > been a part of LLVM itself. > > * > > PolyhedralInfo, which exposes a subset of Polly’s loop analysis for > use by other clients, is now available. > > * > > Polly is now part of the LLVM release process and is being included > with LLVM by various packagers (e.g., Debian). > > > I believe that the LLVM commun...