search for: checkout_isl

...wnload that version when building. However, it would also be > more difficult to both sources in-sync in the checkout (think of git > bisect). > > I suppose these were also the reasons why Polly imported the isl > source in commit r228193 instead of requiring users to call > utils/checkout_isl.sh manually. > > > The other design decisions and rationales are mentioned in the review > summary [2]. I repeat them here so they can be referred to in replies. > > * The library is named LLVMISL and contained in the lib/ISL folder to > work best with LLVM's component syst...

...wnload that version when building. However, it would also be > more difficult to both sources in-sync in the checkout (think of git > bisect). > > I suppose these were also the reasons why Polly imported the isl > source in commit r228193 instead of requiring users to call > utils/checkout_isl.sh manually. > > > The other design decisions and rationales are mentioned in the review > summary [2]. I repeat them here so they can be referred to in replies. > > * The library is named LLVMISL and contained in the lib/ISL folder to > work best with LLVM's component syst...

...ing. However, it would also be > > more difficult to both sources in-sync in the checkout (think of git > > bisect). > > > > I suppose these were also the reasons why Polly imported the isl > > source in commit r228193 instead of requiring users to call > > utils/checkout_isl.sh manually. > > > > > > The other design decisions and rationales are mentioned in the review > > summary [2]. I repeat them here so they can be referred to in replies. > > > > * The library is named LLVMISL and contained in the lib/ISL folder to > > work...

...1 and a CMake script would download that version when building. However, it would also be more difficult to both sources in-sync in the checkout (think of git bisect). I suppose these were also the reasons why Polly imported the isl source in commit r228193 instead of requiring users to call utils/checkout_isl.sh manually. The other design decisions and rationales are mentioned in the review summary [2]. I repeat them here so they can be referred to in replies. * The library is named LLVMISL and contained in the lib/ISL folder to work best with LLVM's component system. The component's name &qu...

...> > > more difficult to both sources in-sync in the checkout (think of git > > > bisect). > > > > > > I suppose these were also the reasons why Polly imported the isl > > > source in commit r228193 instead of requiring users to call > > > utils/checkout_isl.sh manually. > > > > > > > > > The other design decisions and rationales are mentioned in the review > > > summary [2]. I repeat them here so they can be referred to in replies. > > > > > > * The library is named LLVMISL and contained in the lib...

...;> more difficult to both sources in-sync in the checkout (think of git >>>> bisect). >>>> >>>> I suppose these were also the reasons why Polly imported the isl >>>> source in commit r228193 instead of requiring users to call >>>> utils/checkout_isl.sh manually. >>>> >>>> >>>> The other design decisions and rationales are mentioned in the review >>>> summary [2]. I repeat them here so they can be referred to in replies. >>>> >>>> * The library is named LLVMISL and containe...

...wnload that version when building. However, it would also be > more difficult to both sources in-sync in the checkout (think of git > bisect). > > I suppose these were also the reasons why Polly imported the isl > source in commit r228193 instead of requiring users to call > utils/checkout_isl.sh manually. > > > The other design decisions and rationales are mentioned in the review > summary [2]. I repeat them here so they can be referred to in replies. > > * The library is named LLVMISL and contained in the lib/ISL folder to > work best with LLVM's component syst...