search for: isl

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 feedback on the general approach. As Philip suggested in the review, I am reaching out with an RFC with a wider audience on llvm-dev. As fo...

...his 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 import Polly. > > > > I already prepared a patch [2], unfortunately without feedback on the > > general approach. As Philip suggested in the review, I am reaching out >...

...1-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 import Polly. > > > > > > I already prepared a patch [2], unfortunately without feedback on the > > > general approach. As Philip suggested in the revie...

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 import Polly. > > I already prepared a patch [2], unfortunately without feedback on the > general approach. As Philip suggested in the review, I am reaching out > with an RFC with a wider...

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 feedback on the > general approach. As Philip suggested in the review, I am reaching out > with an RFC with a wider...

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 regression tests > > compare the string output of set representation, which unfortunately > > can change between versions. For instance, if a n...

...T+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 import Polly. >>>> >>>> I already prepared a patch [2], unfortunately without feedback on the >>>> general approach. As Philip suggested in...

2018-01-18 6:40 GMT+01:00 Chris Lattner <clattner at nondot.org>: > Great, I think that that would be a fine approach: you can have the cmake logic detect which version of isl is installed and fail if it is the wrong version. This would address my concern. > The motivation explained in the original email seemed to hinge around the fact that Polly’s unit tests depend on accidental details of ISL that change across releases. If you can fix that, then it seems more pl...

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 feedback on the > general approach. As Philip suggested in the review, I am reaching out > with an RFC with a wider...

On Mon, Jan 15, 2018 at 05:52:02PM +0100, Michael Kruse via llvm-dev wrote: > * The library is named LLVMISL and contained in the lib/ISL folder to > work best with LLVM's component system. The component's name "ISL" was > chosen over "isl" as it matches the capitalization of other > two/three-letter-acronym components. Are the ISL sources themselve put into a namespa...

...> On Jan 18, 2018, at 6:02 AM, Michael Kruse <llvmdev at meinersbur.de> wrote: > > > > 2018-01-18 6:40 GMT+01:00 Chris Lattner <clattner at nondot.org>: > >> Great, I think that that would be a fine approach: you can have the cmake logic detect which version of isl is installed and fail if it is the wrong version. This would address my concern. > > > >> The motivation explained in the original email seemed to hinge around the fact that Polly’s unit tests depend on accidental details of ISL that change across releases. If you can fix that, th...

Sebastian Pop wrote: > Jack Howarth wrote: > > 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 0.11.1/2 and > > cloog 0.18.0. The attached patch eliminates this unexpected XPASS seen with newer isl/clo...

...n 18, 2018, at 6:02 AM, Michael Kruse <llvmdev at meinersbur.de> wrote: >> > >> > 2018-01-18 6:40 GMT+01:00 Chris Lattner <clattner at nondot.org>: >> >> Great, I think that that would be a fine approach: you can have the cmake logic detect which version of isl is installed and fail if it is the wrong version. This would address my concern. >> > >> >> The motivation explained in the original email seemed to hinge around the fact that Polly’s unit tests depend on accidental details of ISL that change across releases. If you can fix t...

...>> Jack Howarth wrote: >>>> 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 0.11.1/2 and >>>> cloog 0.18.0. The attached patch eliminates this unexpected XPASS seen with...

...te: >>>>>> 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 0.11.1/2 and >>>>>> cloog 0.18.0. The attached patch eliminates this unexpected...

...Polly :: CodeGen/single_do_loop_int_max_iterations.ll >>> Polly :: CodeGen/single_do_loop_scev_replace.ll >> >> I have some guesses for these, but it would be good to get run >> >> llvm-lit -v on these three test cases. >> >>> Polly :: IslCodeGen/single_loop_param_less_equal.ll >>> Polly :: IslCodeGen/single_loop_param_less_than.ll > > Tobias, > I am unclear on how I should modify the 'make polly-test' run in order > for 'llvm-lit -v' to take effect and where to look for the additional i...

...t;>> 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 0.11.1/2 and > >>>>>>> cloog 0.18.0. The attached patch eliminat...

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 0.11.1/2 and cloog 0.18.0. The attached patch eliminates this unexpected XPASS seen with newer isl/cloog. Jac...

...k Howarth wrote: >>>>> 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 0.11.1/2 and >>>>> cloog 0.18.0. The attached patch eliminates this unexpected XPASS s...

...>>>>> 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 0.11.1/2 and >>>>>>> cloog 0.18.0. The attached patch eliminates this un...