1On Wed, 27 Oct 2004 11:46:07 +0200, C�dric Bastoul
2<cedric.bastoul@prism.uvsq.fr> wrote:
3
4>> Hi Michael,
5>> here is CLooG GMP (a light version of the future CLooG 1.0, with still
6>> some memory leaks and bugs). You should get and build the GMP library
7>> (http://www.swox.com/gmp/ ) and build the PolyLib GMP
8>> (http://icps.u-strasbg.fr/polylib/ then use the option
9>> --with-libgmp=/gmp_install_directory for the configure script). For
10>> CLooG you have to use the --with-bits=gmp and
11>> --with-libgmp=/gmp_install_directory for the configure script. There is
12>> no -cpp option in this CLooG version, I hope you don't use it. Be aware
13>> that your example needs a lot of memory (more than 256MB), I did not
14>> succeed to find the result on my laptop, but at least there were no
15>> other problems.
16>> Good luck, please feel free to send me some feedbacks about this
17>> version, and please, please, do not distribute it.
18>> Cheers,
19>> 
20>> Cedric
21
22
23Hello Cedric,
24
25I'd like to thank you for your very quick response to my problem. I
26tried to build CLooG-GMP with our version of Polylib5.11.1 with
27gmp-support enabled. The only problem that occured to me was that I
28had to include "-lgmp" to the default library-flags in CLooG's
29makefile.in.
30
31Also, I always have a little trouble, because we use polylib as a
32statically linked library, but there is no target in the CLooG
33makefile for building the executable using static linking. It's no big
34deal, I just add a little "-static" to the linking options. I don't
35know if it would be usefull to others, but as you provide a static and
36shared option for the CLooG library targets, could you think about
37providing a similar option for the executable, too? Again, that is
38only a very minor issue, I don' want to waste your time on things like
39that... 
40
41One more important thing: there is that "MAX_RAYS" constant that is
42hard-coded to 200 in the domain.h file. This is simply too low for
43most of my bigger examples. I think it would be quite usefull in the
44future to give an additional option for CLooG to set the number of
45MAX_RAYS without having to re-compile CLooG.
46
47At the moment, I try to get my example done, CLooG has been running
48now for about 50min on my Athlon-64 with 2GB physical and 4GB swap
49memory (of which CLooG is using 2.5GB at the moment). 
50I doubt that it will finish with a result, but that is simply because
51the example seems to be too difficult (although I still don't see how
52I could reduce it...).
53
54Thanks again for the GMP-version! 
55
56greetings,
57Michael
58
59
60