similar to: RFC: Import of Integer Set Library into LLVM source tree

Hi, Nadav, Chris, et al., If you've not already seen it, we had a long discussion about incorporating Polly into LLVM on llvm-dev, http://lists.llvm.org/pipermail/llvm-dev/2017-September/117063.html (with a continuation in October: http://lists.llvm.org/pipermail/llvm-dev/2017-October/118125.html) with a lot of detailed information. I think it is important, first, that we agree on the goals

Thanks Tobias, I am really looking forward to trying out the true integrated Polly and I hope to provide good positive feedback. Since I am maintaining an "out of tree" target, I generally update on each release - I call it the Big Bang update because of the difficulties this presents. At the moment our target is based on the v5.0.0 sources, and I hope to update to the v6.0.0 sources

Dear LLVM community, hope all of you had a good start into 2018 and a quiet branching of LLVM 6.0. With the latest LLVM release out of the way and a longer development phase starting, we would like to restart the process of including Polly and isl into core LLVM to bring changes in early on before the next LLVM release. Short summary: * Today Polly is already part of each LLVM release (and

Hi Tobi,  I have some concerns about adding Polly into LLVM proper. I think that it's great that Polly is a part of the LLVM umbrella of projects, like Clang and LLDB. However, I am not convinced that Polly belongs in the LLVM compiler library. LLVM is a major dependency for so many external projects. Rust, Swift, GPU drivers by different vendors, and JIT compilers all rely on LLVM. Projects

[add subject] Dear LLVM community, hope all of you had a good start into 2018 and a quiet branching of LLVM 6.0. With the latest LLVM release out of the way and a longer development phase starting, we would like to restart the process of including Polly and isl into core LLVM to bring changes in early on before the next LLVM release. Short summary: * Today Polly is already part of each LLVM

On Mon, Sep 4, 2017, at 22:14, Adve, Vikram Sadanand wrote: > Responses inline, marked with (***VSA***) because Outlook on a Mac sucks > for inline replies! > > > On 9/4/17, 2:14 PM, "Tobias Grosser" <tobias.grosser at inf.ethz.ch> wrote: > > On Mon, Sep 4, 2017, at 20:49, Hal Finkel via llvm-dev wrote: > > [tying to original thread] >

On Wed, Jan 17, 2018, at 07:22, Chris Lattner via llvm-dev wrote: > > On Jan 15, 2018, at 8:52 AM, Michael Kruse via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > As for the main motivation on why to import the entire source of isl at all: > > Polly interacts relative tightly with isl which provide the main > > optimization algorithms. For instance, Polly's

On Mon, Sep 4, 2017, at 20:49, Hal Finkel via llvm-dev wrote: > [tying to original thread] > > On 09/04/2017 01:37 PM, Adve, Vikram Sadanand via llvm-dev wrote: > > Hal, Tobias, et al. – > > > > I am strongly in favor of seeing a broader range of loop transformations, supported by strong dependence analysis, added to LLVM, and the Polly infrastructure seems to be by far

It would be great to get "accurate" dependence analysis from polyhedral framework. Anyone working on making polly into analysis+Transforms framework? -Prashantha -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Sahasrabuddhe, Sameer Sent: Monday, October 08, 2012 9:03 AM To: Hal Finkel; Javed Absar Cc: llvmdev at

Dear all, please find below the meeting notes form the Polly BoF (as taken by Michael Kruse). Comments and feedback is very much appreciated. Best, Tobias Status update * Polly late in pipeline * Uses TargetTransformInfo * Part of the release process * isl: C++ interface, MIT licenced, improved scheduler * Polly integration plan; result: isl and Polly available in each build * Better

Hi Sjoerd, On 09/20, Sjoerd Meijer wrote: > I have not been following the polyhedral developments in both GCC and > LLVM very closely the last few years, but I was just wondering if > there are any lessons learned we should look at (or actually already > aware of) in GCC's implementation and integration of Graphite. For > example, do we know if it is (still) enabled/used/etc.?

> On Jan 17, 2018, at 12:14 AM, Tobias Grosser <tobias.grosser at inf.ethz.ch> wrote: >> I have significant concerns about including ISL into LLVM. LLVM >> intentionally takes a very conservative approach to bundling third party >> code with itself: we prefer instead of have them be external >> dependencies that are conditionally configured in on demand. >

On Tue, Sep 26, 2017, at 00:03, Johannes Doerfert wrote: > Hi Hal, > > On 09/22, Hal Finkel wrote: > > Hi, Johannes, > > > > Thanks for writing this. I certainly think you have the right idea in terms > > of the desired end state and modular design. > > Thanks for the feedback! > > > > On 09/19/2017 07:33 PM, Johannes Doerfert wrote: >

On 01/15/2018 08:52 AM, Michael Kruse via llvm-dev wrote: > Dear community, > > for our goal to make polyhedral optimization available in the main > LLVM source, we will need the Integer Set Library (isl)[1]. It is the > main dependency of Polly, but would be required even if we do not > directly import Polly. > > I already prepared a patch [2], unfortunately without

On Tue, Jan 16, 2018, at 08:53, Tobias Grosser via llvm-dev wrote: > On Mon, Jan 15, 2018, at 22:10, Philip Pfaffe via llvm-dev wrote: > > Hi Micheal, > > > > thanks for moving this forward! > > > > 2018-01-15 17:52 GMT+01:00 Michael Kruse via llvm-dev < > > llvm-dev at lists.llvm.org>: > > > > > Dear community, > > > >

Hi Micheal, thanks for moving this forward! 2018-01-15 17:52 GMT+01:00 Michael Kruse via llvm-dev < llvm-dev at lists.llvm.org>: > Dear community, > > for our goal to make polyhedral optimization available in the main > LLVM source, we will need the Integer Set Library (isl)[1]. It is the > main dependency of Polly, but would be required even if we do not > directly

Hi Hal, On 09/22, Hal Finkel wrote: > Hi, Johannes, > > Thanks for writing this. I certainly think you have the right idea in terms > of the desired end state and modular design. Thanks for the feedback! > On 09/19/2017 07:33 PM, Johannes Doerfert wrote: > >Hi Hal, Tobias, Michael, and others, > > > >I'd like to add my view (and a proposal) to this

> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On > Behalf Of Hal Finkel > Sent: Monday, October 08, 2012 1:35 AM > > I'd like to add that, mostly through Tobi's efforts, we were able to have isl (the > integer set library) on which Polly depends relicensed such that it is now > distributed under the MIT

On 01/16/2018 01:59 AM, Tobias Grosser via llvm-dev wrote: > On Tue, Jan 16, 2018, at 08:53, Tobias Grosser via llvm-dev wrote: >> On Mon, Jan 15, 2018, at 22:10, Philip Pfaffe via llvm-dev wrote: >>> Hi Micheal, >>> >>> thanks for moving this forward! >>> >>> 2018-01-15 17:52 GMT+01:00 Michael Kruse via llvm-dev < >>> llvm-dev at

On 01/15/2018 10:52 AM, Michael Kruse via llvm-dev wrote: > Dear community, > > for our goal to make polyhedral optimization available in the main > LLVM source, we will need the Integer Set Library (isl)[1]. It is the > main dependency of Polly, but would be required even if we do not > directly import Polly. > > I already prepared a patch [2], unfortunately without