This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Support official CLooG.org versions.


Hi again,

it seems that I have a problem with the following scenario:

I have a cloog-ppl installed in /usr/local/lib (a legacy one).
Now, I have also a new cloog-isl installed in one of my home
directories (/home/konrad/cloog-isl).

I configure it with: ./configure --with-cloog=/home/konrad/cloog-isl/lib

Now, it seems I'm not able to override the order in which
a configuration script is looking for cloog libraries.

It first tries a legacy one (linking with -lcloog).
It finds that there is indeed a legacy cloog in /usr/local/lib
and it is not even trying "-lcloog-isl" with the value
--with-cloog=/home/konrad/cloog-isl/lib.

I think we need some prioritizing mechanism. Let's say, that if you could find
both legacy and isl-cloog then the priority should be given to the isl-cloog.
But, this is not a good solution either. It seems that if we can find multiple
valid cloog installations, an user should be able to manually override the
desired cloog version.

I'm not a configuration scripts expert.
I'm not sure whether this solution would be accepted by GCC community,
but I propose the following:

have a flag called "--with-cloog" that can take several values, for
example "auto", "isl", "ppl", "no" etc.

Then, have other flag called "--with-cloog-prefix" that gives a path
to the place where we should be looking for a cloog.

Konrad



2010/9/12 Konrad Trifunovic <konrad.trifunovic@gmail.com>:
> Hi,
>
> just a short comment/question:
>
>> + ?# Only fail if the user explicitly selected CLooG.
>> + ?cloog_allow_fail=no
>> + ?if test "${with_cloog+set}" = set \
>> + ? ?|| test "${with_cloog_include+set}" = set \
>> + ? ?|| test "${with_cloog_lib+set}" = set ; then
>> + ? ?cloog_allow_fail=yes
>> + ?fi
>
> It seems that 'cloog_allow_fail' would be set to YES, if
> we enable one of the flags. But if we enable all the
> flags (with_cloog, with_cloog_include, with_cloog_lib)
> then it would remain NO. Is this intended?
>
> Konrad
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]