search for: scopbuild

...ike this direction. In general, we may want to decouple the > ScopDetection/ScopInfo construction logic from the pass logic, such that we > can run the logic ScopDetection and ScopInfo construction in a function > pass, call graph scc pass, or even a loop pass. Totally agreed. Some kind of ScopBuilder interface that can be queried would be perfect. Additionally a DependenceBuilder. I would imagine something along the lines of: Passes: ScopInfo <-----------[depends]----------- DependenceInfo | | [queries]...

...neral, we may want to decouple the > > ScopDetection/ScopInfo construction logic from the pass logic, such that > we > > can run the logic ScopDetection and ScopInfo construction in a function > > pass, call graph scc pass, or even a loop pass. > Totally agreed. Some kind of ScopBuilder interface that can be queried > would be perfect. Additionally a DependenceBuilder. > > I would imagine something along the lines of: > > > Passes: ScopInfo <-----------[depends]----------- DependenceInfo > |...

...o decouple the >> > ScopDetection/ScopInfo construction logic from the pass logic, such >> that we >> > can run the logic ScopDetection and ScopInfo construction in a function >> > pass, call graph scc pass, or even a loop pass. >> Totally agreed. Some kind of ScopBuilder interface that can be queried >> would be perfect. Additionally a DependenceBuilder. >> >> I would imagine something along the lines of: >> >> >> Passes: ScopInfo <-----------[depends]----------- DependenceInfo >> |...

Hi Johannes, On Mon, Mar 21, 2016 at 6:35 PM, Johannes Doerfert < doerfert at cs.uni-saarland.de> wrote: > Hey Utpal, > > First of, I think you made nice process here and have some very good > ideas of what we could do in the future. > > [NOTE: I CC'ed some people that have shown interest in this topic but I > might have forgotten some, therefor I also added the

Hey Utpal, First of, I think you made nice process here and have some very good ideas of what we could do in the future. [NOTE: I CC'ed some people that have shown interest in this topic but I might have forgotten some, therefor I also added the llvm-dev list.] For the upcoming GSoC proposal we should slow down a little bit and reevaluate our goals. After talking to a couple of LLVM and

...e it. Instead there is a C++ interface in-between that encapsulates the features needed. Once our use cases are clear we can re-implement this interface. ** For comparison, the value analysis covers parts of the ScopDetection, all of SCEVValidator and SCEVAffinator as well as parts of ScopInfo and ScopBuilder in Polly. *** The memory analysis is concerned with the construction and functionality Polly implements in the MemoryAccess class. **** The dependence analysis is similar to Polly's DependenceInfo class but is supposed to allow more fine-grained control. --- These are a few design decisions...

...interface in-between that > encapsulates the features needed. Once our use cases are clear we can > re-implement this interface. > > ** For comparison, the value analysis covers parts of the ScopDetection, > all of SCEVValidator and SCEVAffinator as well as parts of ScopInfo and > ScopBuilder in Polly. > *** The memory analysis is concerned with the construction and > functionality Polly implements in the MemoryAccess class. > **** The dependence analysis is similar to Polly's DependenceInfo class > but is supposed to allow more fine-grained control. Is the code for t...

...ead there is a C++ interface in-between that encapsulates the features needed. Once our use cases are clear we can re-implement this interface. > > ** For comparison, the value analysis covers parts of the ScopDetection, all of SCEVValidator and SCEVAffinator as well as parts of ScopInfo and ScopBuilder in Polly. > *** The memory analysis is concerned with the construction and functionality Polly implements in the MemoryAccess class. > **** The dependence analysis is similar to Polly's DependenceInfo class but is supposed to allow more fine-grained control. > > --- > > Th...

...> >encapsulates the features needed. Once our use cases are clear we can > >re-implement this interface. > > > >** For comparison, the value analysis covers parts of the ScopDetection, > >all of SCEVValidator and SCEVAffinator as well as parts of ScopInfo and > >ScopBuilder in Polly. > >*** The memory analysis is concerned with the construction and > >functionality Polly implements in the MemoryAccess class. > >**** The dependence analysis is similar to Polly's DependenceInfo class > >but is supposed to allow more fine-grained control. &g...

** *Hi everyone,As you may know, stock LLVM does not provide the kind of advanced loop transformations necessary to provide good performance on many applications. LLVM's Polly project provides many of the required capabilities, including loop transformations such as fission, fusion, skewing, blocking/tiling, and interchange, all powered by state-of-the-art dependence analysis. Polly also