April 2009 - PPL-devel - BUGSENG Mailman

Re: [PPL-devel] GMP 4.3.0 released
by Dennis Clarke 15 Apr '09

15 Apr '09

> Torbjorn Granlund wrote: >> It is my great pleasure to announce the availability a new major release >> of >> the GNU Multiple Precision Arithmetic Library (GMP). The new release is >> identified as 4.3.0. > > Hi Torbjorn, > > congratulations and thank you for the new release. > With the most minor tweak it builds fine on Solaris : ABI=32 $ ls .libs/lib* .libs/libgmp.a .libs/libgmp.so.3 .libs/libgmpxx.lai .libs/libgmp.la .libs/libgmp.so.3.5.0 .libs/libgmpxx.so .libs/libgmp.lai .libs/libgmpxx.a .libs/libgmpxx.so.4 .libs/libgmp.so .libs/libgmpxx.la .libs/libgmpxx.so.4.1.0 $ $ $ file .libs/libgmp.so.3.5.0 .libs/libgmp.so.3.5.0: ELF 32-bit MSB dynamic lib SPARC Version 1, dynamically linked, not stripped $ file .libs/libgmpxx.so.4.1.0 .libs/libgmpxx.so.4.1.0: ELF 32-bit MSB dynamic lib SPARC Version 1, dynamically linked, not stripped and ABI=64 $ file .libs/libgmp.so.3.5.0 .libs/libgmp.so.3.5.0: ELF 64-bit MSB dynamic lib SPARCV9 Version 1, dynamically linked, not stripped $ file .libs/libgmpxx.so.4.1.0 .libs/libgmpxx.so.4.1.0: ELF 64-bit MSB dynamic lib SPARCV9 Version 1, dynamically linked, not stripped All tests pass for libgmp.so.3.5.0 however I have to get in and manually run the tests for the cxx libs. Dennis Clarke http://www.blastwave.org

1 0

[Fwd: Re: Parma Polyhedra Library 0.10.1]
by Roberto Bagnara 15 Apr '09

15 Apr '09

He did not read the P.S... -------- Original Message -------- Subject: Re: Parma Polyhedra Library 0.10.1 Date: Wed, 15 Apr 2009 10:53:28 -0400 From: Jack Howarth <howarth(a)bromo.med.uc.edu> To: Roberto Bagnara <bagnara(a)cs.unipr.it> CC: gcc(a)gcc.gnu.org References: <20090415120051.GA28541(a)bromo.med.uc.edu> <84fc9c000904150544h1d89f442k7ba094128196228e(a)mail.gmail.com> <20090415131934.GB29025(a)bromo.med.uc.edu> <49E5F0D4.4070105(a)cs.unipr.it> On Wed, Apr 15, 2009 at 04:36:04PM +0200, Roberto Bagnara wrote: > Jack Howarth wrote: >> On Wed, Apr 15, 2009 at 02:44:12PM +0200, Richard Guenther wrote: >>> On Wed, Apr 15, 2009 at 2:00 PM, Jack Howarth <howarth(a)bromo.med.uc.edu> wrote: >>>> [...] >>>> It seems rather bad form to me that soversions are being changed in >>>> minor dot releases of ppl. This has been one of my biggest fears >>>> about cloog/ppl...that the so version control be randomly bumped. > > Jack, > > can you please explain what you mean by "randomly bumped"? > Thanks, > Roberto, I think there is a common misunderstanding on darwin about the meaning of the compatibility level. I (and others) have been under the impression that the compatibility level should be exactly one more than the major soversion. For instance, the fftw3 3.2.1 release bumped the compatibility level by one compared to the major soversion and the package was never updated because this was viewed as an error upstream. My understanding now is that the relationship is rather loose and the compatibility level only need to be at least one higher than the major soversion. Jack > Roberto > > P.S. Please direct all the PPL-related messages to ppl-devel(a)cs.unipr.it > > -- > Prof. Roberto Bagnara > Computer Science Group > Department of Mathematics, University of Parma, Italy > http://www.cs.unipr.it/~bagnara/ > mailto:bagnara@cs.unipr.it -- Prof. Roberto Bagnara Computer Science Group Department of Mathematics, University of Parma, Italy http://www.cs.unipr.it/~bagnara/ mailto:bagnara@cs.unipr.it

1 0

[GIT] ppl/ppl(master): Accommodate version 4.3.0 of GMP.
by Roberto Bagnara 15 Apr '09

15 Apr '09

Module: ppl/ppl Branch: master Commit: 5596eca02f2dea09e57ea22a240c2f3eab8be9e5 URL: http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=5596eca02f2d… Author: Roberto Bagnara <bagnara(a)cs.unipr.it> Date: Wed Apr 15 16:03:44 2009 +0200 Accommodate version 4.3.0 of GMP. Starting from GMP version 4.3.0 (released a few hours after PPL 0.10.1), the gmp_version variable always contains three parts. In previous versions the patchlevel was omitted if it was 0. This change broke our GMP detection procedure. --- m4/ac_check_gmp.m4 | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/m4/ac_check_gmp.m4 b/m4/ac_check_gmp.m4 index 541cb36..4dc3bc8 100644 --- a/m4/ac_check_gmp.m4 +++ b/m4/ac_check_gmp.m4 @@ -60,7 +60,12 @@ main() { { std::ostringstream s(header_version); s << __GNU_MP_VERSION << "." << __GNU_MP_VERSION_MINOR; - if (__GNU_MP_VERSION_PATCHLEVEL != 0) + // Starting from GMP version 4.3.0, the gmp_version variable + // always contains three parts. In previous versions the + // patchlevel was omitted if it was 0. + if (__GNU_MP_VERSION_PATCHLEVEL != 0 + || __GNU_MP_VERSION > 4 + || (__GNU_MP_VERSION == 4 && __GNU_MP_VERSION_MINOR >= 3)) s << "." << __GNU_MP_VERSION_PATCHLEVEL; header_version = s.str(); }

1 0

[GIT] /home/abagnara/ppl(master): Accommodate version 4.3.0 of GMP.
by Roberto Bagnara 15 Apr '09

15 Apr '09

Module: /home/abagnara/ppl Branch: master Commit: ca32695fdb3245a195f7704260b947abc338e881 URL: http://www.cs.unipr.it/git/gitweb.cgi?p=/home/abagnara/ppl.git;a=commit;h=c… Author: Roberto Bagnara <bagnara(a)cs.unipr.it> Date: Wed Apr 15 16:03:44 2009 +0200 Accommodate version 4.3.0 of GMP. Starting from GMP version 4.3.0 (released a few hours after PPL 0.10.1), the gmp_version variable always contains three parts. In previous versions the patchlevel was omitted if it was 0. This change broke our GMP detection procedure --- m4/ac_check_gmp.m4 | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/m4/ac_check_gmp.m4 b/m4/ac_check_gmp.m4 index 541cb36..4dc3bc8 100644 --- a/m4/ac_check_gmp.m4 +++ b/m4/ac_check_gmp.m4 @@ -60,7 +60,12 @@ main() { { std::ostringstream s(header_version); s << __GNU_MP_VERSION << "." << __GNU_MP_VERSION_MINOR; - if (__GNU_MP_VERSION_PATCHLEVEL != 0) + // Starting from GMP version 4.3.0, the gmp_version variable + // always contains three parts. In previous versions the + // patchlevel was omitted if it was 0. + if (__GNU_MP_VERSION_PATCHLEVEL != 0 + || __GNU_MP_VERSION > 4 + || (__GNU_MP_VERSION == 4 && __GNU_MP_VERSION_MINOR >= 3)) s << "." << __GNU_MP_VERSION_PATCHLEVEL; header_version = s.str(); }

1 0

Re: [PPL-devel] Parma Polyhedra Library 0.10.1
by Roberto Bagnara 15 Apr '09

15 Apr '09

Jack Howarth wrote: > On Wed, Apr 15, 2009 at 02:44:12PM +0200, Richard Guenther wrote: >> On Wed, Apr 15, 2009 at 2:00 PM, Jack Howarth <howarth(a)bromo.med.uc.edu> wrote: >>> [...] >>> It seems rather bad form to me that soversions are being changed in >>> minor dot releases of ppl. This has been one of my biggest fears >>> about cloog/ppl...that the so version control be randomly bumped. Jack, can you please explain what you mean by "randomly bumped"? Thanks, Roberto P.S. Please direct all the PPL-related messages to ppl-devel(a)cs.unipr.it -- Prof. Roberto Bagnara Computer Science Group Department of Mathematics, University of Parma, Italy http://www.cs.unipr.it/~bagnara/ mailto:bagnara@cs.unipr.it

1 0

[GIT] ppl/ppl(master): Accommodate version 4.3.0 of GMP.
by Roberto Bagnara 15 Apr '09

15 Apr '09

Module: ppl/ppl Branch: master Commit: b0652f33a69df21730b07ac57edf0e4e85789d94 URL: http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=b0652f33a69d… Author: Roberto Bagnara <bagnara(a)cs.unipr.it> Date: Wed Apr 15 16:03:44 2009 +0200 Accommodate version 4.3.0 of GMP. Starting from GMP version 4.3.0 (released a few hours after PPL 0.11), the gmp_version variable always contains three parts. In previous versions the patchlevel was omitted if it was 0. This change broke our GMP detection procedure --- m4/ac_check_gmp.m4 | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/m4/ac_check_gmp.m4 b/m4/ac_check_gmp.m4 index 541cb36..4dc3bc8 100644 --- a/m4/ac_check_gmp.m4 +++ b/m4/ac_check_gmp.m4 @@ -60,7 +60,12 @@ main() { { std::ostringstream s(header_version); s << __GNU_MP_VERSION << "." << __GNU_MP_VERSION_MINOR; - if (__GNU_MP_VERSION_PATCHLEVEL != 0) + // Starting from GMP version 4.3.0, the gmp_version variable + // always contains three parts. In previous versions the + // patchlevel was omitted if it was 0. + if (__GNU_MP_VERSION_PATCHLEVEL != 0 + || __GNU_MP_VERSION > 4 + || (__GNU_MP_VERSION == 4 && __GNU_MP_VERSION_MINOR >= 3)) s << "." << __GNU_MP_VERSION_PATCHLEVEL; header_version = s.str(); }

1 0

Re: [PPL-devel] Parma Polyhedra Library 0.10.1
by Roberto Bagnara 15 Apr '09

15 Apr '09

Richard Guenther wrote: > On Tue, Apr 14, 2009 at 3:02 PM, Roberto Bagnara <bagnara(a)cs.unipr.it> wrote: >> We are pleased to announce the availability of PPL 0.10.1, a new release >> of the Parma Polyhedra Library. > > It seems to build and test ok on {i586,ia64,ppc,ppc64,s390,x86_64}-linux > but I get > > PASS: nnc_writepolyhedron1 > /bin/sh: line 4: 29952 Segmentation fault ${dir}$tst > FAIL: memory1 > ====================================== > 1 of 191 tests failed > Please report to ppl-devel(a)cs.unipr.it > ====================================== > > on s390x-linux. Does the testsuite stop after the first error? Hi Richard. The testsuite does not proceed after the first directory that gives an error. In your case, the `tests/Polyhedron' directory produced that error and the `tests/Grid' directory is the only subdirectory of `tests' that has not been tested because of that error. > If not, > what is memory1 testing? It tests the PPL features that allow to recover after an out-of-memory error, i.e., when std::bad_alloc is thrown. It does so by limiting the amount of memory available to the process, attempting some expensive computation, catching std:bad_alloc, and restart. The key function is this one: bool guarded_compute_open_hypercube_generators(dimension_type dimension, unsigned long max_memory_in_bytes) { try { limit_memory(max_memory_in_bytes); compute_open_hypercube_generators(dimension); return true; } catch (const std::bad_alloc&) { nout << "out of virtual memory" << endl; return false; } catch (...) { exit(1); } // Should never get here. exit(1); } From the fact that you observe this failure, I gather that the configure script found a version of GMP compiled with -fexceptions. Unfortunately, this is not always enough. For instance, on the Itanium the test fails because of the libunwind bug reported in http://lists.gnu.org/archive/html/libunwind-devel/2008-09/msg00001.html Hence the test is disabled if defined(__ia64). I don't know what the problem could be on s390x-linux. Do you know if there is an s390x-linux machine we can obtain access to for the purpose of debugging? Cheers, Roberto -- Prof. Roberto Bagnara Computer Science Group Department of Mathematics, University of Parma, Italy http://www.cs.unipr.it/~bagnara/ mailto:bagnara@cs.unipr.it

3 2

[GIT] ppl/ppl(deprecated_0_11_removal): Initiated the removal of the methods deprecated in PPL 0.10.
by Roberto Bagnara 14 Apr '09

14 Apr '09

Module: ppl/ppl Branch: deprecated_0_11_removal Commit: 51a19a2a50729a16573d6577717d39432ffce921 URL: http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=51a19a2a5072… Author: Roberto Bagnara <bagnara(a)cs.unipr.it> Date: Tue Apr 14 22:13:49 2009 +0200 Initiated the removal of the methods deprecated in PPL 0.10. --- NEWS | 15 ++ interfaces/C/ppl_interface_generator_c_cc_code.m4 | 39 ---- interfaces/C/ppl_interface_generator_c_h_code.m4 | 27 --- ...l_interface_generator_c_procedure_generators.m4 | 3 - .../ppl_interface_generator_prolog_cc_code.m4 | 78 ------- .../ppl_interface_generator_prolog_hh_code.m4 | 21 -- ...erface_generator_prolog_procedure_generators.m4 | 6 +- interfaces/ppl_interface_generator_common_dat.m4 | 7 - src/BD_Shape.defs.hh | 132 ----------- src/BD_Shape.inlines.hh | 60 ----- src/Grid.defs.hh | 210 ----------------- src/Grid.inlines.hh | 24 -- src/Grid_public.cc | 131 ----------- src/Pointset_Powerset.defs.hh | 80 ------- src/Pointset_Powerset.inlines.hh | 8 - src/Pointset_Powerset.templates.hh | 66 ------ src/Polyhedron.defs.hh | 223 ------------------ src/Polyhedron.inlines.hh | 17 -- src/Polyhedron_public.cc | 240 -------------------- tests/Powerset/addconstraints1.cc | 17 ++- tests/Powerset/intersection1.cc | 6 +- 21 files changed, 34 insertions(+), 1376 deletions(-) Diff: http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commitdiff;h=51a19a2a…

1 0

[GIT] ppl/ppl(deprecated_0_11_removal): Improved.
by Roberto Bagnara 14 Apr '09

14 Apr '09

Module: ppl/ppl Branch: deprecated_0_11_removal Commit: 23cb7dad8cf9db38bca9ac8e59c5602edb860910 URL: http://www.cs.unipr.it/git/gitweb.cgi?p=ppl/ppl.git;a=commit;h=23cb7dad8cf9… Author: Roberto Bagnara <bagnara(a)cs.unipr.it> Date: Tue Apr 14 14:09:48 2009 +0200 Improved. --- doc/README.doc | 13 +++++++------ 1 files changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/README.doc b/doc/README.doc index 3fd2c80..57f95ff 100644 --- a/doc/README.doc +++ b/doc/README.doc @@ -56,7 +56,7 @@ The Documentation You May Build Yourself ======================================== When all else fails (which is the case, for example, when you are -using a git version [1]) then you may build the documentation by +using a Git version [1]) then you may build the documentation by yourself. In order to do that, you should have a recent version of Doxygen [2] and, if you want to build the HTML documentation, a recent version of Graphviz [3]. When you have all the tools installed and @@ -100,16 +100,16 @@ command `make world' will build all the available documentation in all of the above formats. It is possible that, while compiling some PostScript or PDF -documentation, LaTeX dies with a "TeX capacity exceeded" error +documentation, TeX dies with a "TeX capacity exceeded" error message. The error should contain the indication of the TeX buffer whose capacity has been exceeded, e.g.: ! TeX capacity exceeded, sorry [save size=5000]. -You then need to edit the LaTeX configuration file that defines the +You then need to edit the TeX configuration file that defines the buffer sizes so as to increase the value of the relevant buffer. Note: the actual name and location of the configuration file will vary -depending on the available LaTeX distribution: possible names include +depending on the available TeX distribution: possible names include texmf.cnf, texmf.cfg and 20sizes.cnf. Continuing our example, we can double save_size by editing the configuration file so that the relevant line becomes @@ -117,11 +117,12 @@ relevant line becomes save_size = 10000 % for saving values outside current group Any change to such configuration files should be followed by running -the command +a command like texconfig init -for the change to become effective. +for the change to become effective (on some systems the `texconfig-sys' +command should be used to configure TeX system-wide). --------

1 0

[Fwd: Re: Parma Polyhedra Library 0.10.1]
by Roberto Bagnara 14 Apr '09

14 Apr '09

-------- Original Message -------- Subject: Re: Parma Polyhedra Library 0.10.1 Date: Tue, 14 Apr 2009 17:51:33 +0200 From: Richard Guenther <richard.guenther(a)gmail.com> To: Roberto Bagnara <bagnara(a)cs.unipr.it> CC: GCC Mailing List <gcc(a)gcc.gnu.org> References: <49E48948.60300(a)cs.unipr.it> On Tue, Apr 14, 2009 at 3:02 PM, Roberto Bagnara <bagnara(a)cs.unipr.it> wrote: > > We are pleased to announce the availability of PPL 0.10.1, a new release > of the Parma Polyhedra Library. > > This release includes several important improvements to PPL 0.10, > among which is better portability (including the support for > cross-compilation), increased robustness, better packaging and several > bug fixes. The precise list of user-visible changes is available at > http://www.cs.unipr.it/ppl/Download/ftp/releases/0.10.1/NEWS . > For more information, please come and visit the PPL web site at > > http://www.cs.unipr.it/ppl/ > > On behalf of all the past and present contributors listed at > http://www.cs.unipr.it/ppl/Credits/ and in the file CREDITS, > > Roberto Bagnara <bagnara(a)cs.unipr.it> > Patricia M. Hill <hill(a)comp.leeds.ac.uk> > Enea Zaffanella <zaffanella(a)cs.unipr.it> It seems to build and test ok on {i586,ia64,ppc,ppc64,s390,x86_64}-linux but I get PASS: nnc_writepolyhedron1 /bin/sh: line 4: 29952 Segmentation fault ${dir}$tst FAIL: memory1 ====================================== 1 of 191 tests failed Please report to ppl-devel(a)cs.unipr.it ====================================== on s390x-linux. Does the testsuite stop after the first error? If not, what is memory1 testing? Thanks, Richard. -- Prof. Roberto Bagnara Computer Science Group Department of Mathematics, University of Parma, Italy http://www.cs.unipr.it/~bagnara/ mailto:bagnara@cs.unipr.it

1 0