[llvm-dev] RFC: Import of Integer Set Library into LLVM source tree

Chris Lattner via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 23 22:42:10 PST 2018

> On Jan 19, 2018, at 6:56 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 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 namespace under llvm? That's my
> primary concern: a program wanting to use a random ISL version and LLVM
> at the same time.

Yes, this can be a very significant problem.  Many highly layered software systems (e.g. TensorFlow) end up with LLVM as a dependency (e.g. through XLA).  Making ISL a non-encapsulated dependency that LLVM is version locked with will be a significant problem if any of the other layers need to use ISL, because they will be version locked to the same revision even if they themselves don’t depend on LLVM...


More information about the llvm-dev mailing list