This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 0/3] Configure support for official CLooG versions.
On 08/12/2010 12:33 AM, Joseph S. Myers wrote:
> On Thu, 12 Aug 2010, Andreas Simbuerger wrote:
>
>> The Integer Set Library (ISL) is used within CLooG's backend instead
>> of the PPL (Another backend using the PolyLib is available too).
>> The official CLooG version provides it's own ISL bundle which
>> get's installed alongside CLooG itself. The ISL is exclusively used by
>> CLooG for now.
> Do you mean that ISL is a part of the libcloog-isl library, so that no
> separate -lisl option is ever going to be needed when linking anything (in
> particular, when using static libraries so shared library dependencies are
> not available)? There are several questions:
>
> * Is ISL source part of the CLooG tarball or a separate tarball? If a
> separate tarball, install.texi needs to explain this.
>
The ISL is in fact a separate library, but the CLooG tarball is bundled
with a working release of it. You can configure CLooG with an out-of-tree
ISL version, but the default setting is to use the bundled ISL.
By default CLooG's ISL gets installed into CLooG's install dir and is
covered
by CLooG's library path.
> * Is ISL included in the libcloog-isl library binary or is it a separate
> library binary? If a separate binary, the configure code needs to link
> against it explicitly.
As mentioned above, it is a separate library. I don't fully understand why
it is required to link to unused code? The ISL is never required by GCC.
Ideally i do not want to know which backend CLooG is using for its'
code generation.
> * Does ISL depend on other libraries, like PPL depends on -lgmp -lgmpxx
> -lstdc++? If so, then the configure code needs to know about these and if
> libstdc++ is involved then the documentation of --with-host-libstdcxx may
> need updating as well.
>
The ISL depends on -lgmp.
Andreas