Gambit-list Septembre 2018

gambit-list@iro.umontreal.ca

5 participants
6 discussions

Gambit versus Python+GMP: Timing for Chudnovskys' algorithm for pi
by Bradley Lucier 07 Avr '22

07 Avr '22

Bakul Shah wrote a particularly elegant Scheme program for Chudnovskys' algorithm for pi based on the Common Lisp program here: https://bitbucket.org/tarballs_are_good/numericl/src/5fe8fe7089f48ab1c8a388… Nick Craig-Wood wrote a Python program using the GMP multiprecision library that appears to use exactly the same algorithm here: http://www.craig-wood.com/nick/articles/pi-chudnovsky/ I modified both programs a bit and include them here. They time the calculation of $10^n$ digits of pi for $n=1,2,3,4,5,6,7$. The results are heine:~/programs/gambiteer/gambit> !py python pi_chudnovsky_bs_gmpy.py 31415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679 ('chudnovsky_gmpy_mpz_bs: digits', 10, 'time', 1.0967254638671875e-05) ('chudnovsky_gmpy_mpz_bs: digits', 100, 'time', 3.0040740966796875e-05) Last 5 digits 70679 OK ('chudnovsky_gmpy_mpz_bs: digits', 1000, 'time', 0.00025582313537597656) Last 5 digits 01989 OK ('chudnovsky_gmpy_mpz_bs: digits', 10000, 'time', 0.00386810302734375) Last 5 digits 75678 OK ('chudnovsky_gmpy_mpz_bs: digits', 100000, 'time', 0.0834801197052002) Last 5 digits 24646 OK ('chudnovsky_gmpy_mpz_bs: digits', 1000000, 'time', 1.655979871749878) Last 5 digits 58151 OK ('chudnovsky_gmpy_mpz_bs: digits', 10000000, 'time', 30.67442488670349) Last 5 digits 55897 OK heine:~/programs/gambiteer/gambit> gsi chud1.scm Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 10, CPU time: 0.. Last 5 digits 26535. Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 100, CPU time: 0.. Last 5 digits 70679. Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 1000, CPU time: .004. Last 5 digits 1989. Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 10000, CPU time: .028. Last 5 digits 75678. Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 100000, CPU time: .472. Last 5 digits 24646. Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 1000000, CPU time: 6.448. Last 5 digits 58151. Chudnovsky's algorithm using binary splitting in Gambit Scheme: digits 10000000, CPU time: 98.612. Last 5 digits 55897. So it appears that for this algorithm applied to large integers, GMP's bignum routines are about 3-4 times as fast as Gambit's bignum routines. Not so bad. For smaller bignums, GMP has a bigger advantage. The C program gmp-chudnovsky.c includes certain optimizations to this basic algorithm: http://gmplib.org/pi-with-gmp.html ftp://ftp.gmplib.org/pub/misc/gmp-chudnovsky.c On my machine, compiled with gcc -O3 -march=native -o gmp-chudnovsky gmp-chudnovsky.c -lgmp -lm the CPU times for 1,000,000 and 10,000,000 digits are 1.064 and 18.200 seconds, respectively. This is with a somewhat older machine model name : Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz running Ubuntu 13.04 with heine:~/programs/gambiteer/gambit> gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.7.3-1ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --with-system-zlib --enable-objc-gc --with-cloog --enable-cloog-backend=ppl --disable-cloog-version-check --disable-ppl-version-check --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) heine:~/programs/gambiteer/gambit> gsi -v v4.6.9 20130607151908 x86_64-unknown-linux-gnu "./configure '--enable-single-host' '--enable-multiple-versions' '--enable-shared'" and the Ubuntu-provided GMP 5.0.5. (I'm sure the GMP folks have a better way to build GMP on my machine than the "generic" 64-bit version provided by Ubuntu.) Brad

7 18

Native backend
by Marc Feeley 01 Oct '18

01 Oct '18

For those interested in how the native backend for Gambit is progressing, here are some links to the paper that was presented yesterday at the Scheme workshop, and the slides of the talk. Laurent Huberdeau did a great job! http://www.iro.umontreal.ca/~gambit/SW2018-talk.pdf https://www.brinckerhoff.org/scheme2018/papers/Huberdeau_Feeley.pdf Marc

3 3

Problems with Gambit OpenSSL support
by timo.myyra＠bittivirhe.fi 19 Sep '18

19 Sep '18

Hi, I've encountered two different issues with Gambits OpenSSL use. First issue is that it doesn't seem to work with LibreSSL. I tested this on my OpenBSD-current and Gambit compiles just fine but tls support doesn't seem to work: $ gsi Gambit v4.9.0 > (make-tls-context) *** ERROR IN (console)(a)1.1 -- (make-tls-context) 1> Any methods to get further details on what error happened here? LibreSSL should have API compatibility with OpenSSL 1.0.1. Which API the Gambit uses? I asked around on voidlinux IRC and same issue seems to be happening there as well. Void Linux also uses LibreSSL. Another issue I noticed that the Gambit fails to compile at all when its configured with '--enable-openssl' on system using OpenSSL 1.1.0. I tested it with Slackware64-current and it broke on compilation failing to find some SSL context structure. eems there are API changes in later OpenSSL versions which Gambit can't handle currently. Could the docs be updated so that those include which OpenSSL versions should work. Timo

2 2

Gerbil v0.13 is out!
by Dimitris Vyzovitis 06 Sep '18

06 Sep '18

Hi all, I am happy to announce the release of Gerbil v0.13, to go with Gambit v4.9.0. This release was mainly focused on performance improvements, bug fixes, and a brand new documentation site: https://cons.io As usual, for sources and downloads: https://github.com/vyzo/gerbil https://github.com/vyzo/gerbil/releases Release highlights: - New documentation structure, with documentation rendered online at cons.io . - The compiler has been greatly improved, with a new match/syntax-case optimizer and full program optimization for static executables. - The expander has been tuned for performance, resulting in 2x gxi load time reduction. - R7RS coverage has been greatly improved, fixing most modified R5RS procedures to comply to the new specification. Full release changelog: https://github.com/vyzo/gerbil/blob/master/CHANGELOG.md For questions and support, come say hi on #gerbil-scheme in irc.freenode.net . Happy Hacking! -- vyzo

1 0

Building Gambit with Alternate Versions of OpenSSL
by Bob Coleman 06 Sep '18

06 Sep '18

Friends - I recently ran into the OpenSSL 1.1 compatibility issue that others noted on the gitter chat when building Gambit on Ubuntu 18. Ubuntu 18.04 is using the 1.1 version of OpenSSL as default. Downgrading was not an option for me due to other dependencies (namely node 8) on the 1.1 version. OpenSSL version 1.1 introduces several backwards incompatible changes, but Gambit is only using a hand full of those. I have patched os_io.c to allow building with OpenSSL 1.1, but before submitting a pull request I want to make sure building against OpenSSL 1.0 still works properly. Is there a way to configure the Gambit build process to use a locally installed version of OpenSSL 1.0, instead of the system installed OpenSSL 1.1, for testing? I've tried setting the CFLAGS, LDFLAGS, etc environment variables, as below, with no luck. I have also tried building OpenSSL as a static and shared library with the same results. Here are the steps I'm using for building: ./configure make -j8 realclean ./configure make -j8 from-scratch make -j8 bootstrap make bootclean export CFLAGS=" -I/home/user/.local/openssl1.0/include/openssl " export LDFLAGS=" -L/home/user/.local/openssl1.0/lib " export LIBRARY_PATH="/home/user/.local/openssl1.0/lib" export LD_LIBRARY_PATH="/home/user/.local/openssl1.0/lib" ./configure --enable-single-host --enable-poll --enable-openssl --prefix=/home/user/tmp/gambit-test/build make -j8 make check These are the error messages from the make file. It seems to be having trouble finding the library, or maybe it is linking it in the wrong order. Note the flag adding a non-standard OpenSSL location that is always present with --enable-openssl, even through that directory doesn't exsist "-L/usr/local/opt/openssl/lib". Could that be confusing things? making all in gsi make[1]: Entering directory '/home/user/tmp/gambit-test/gambit-src/gsi' gcc -L/home/user/.local/openssl1.0/lib -I/home/user/.local/openssl1.0/include/openssl -Wno-unused -Wno-write-strings -Wdisabled-optimization -fwrapv -fno-strict-aliasing -fno-trapping-math -fno-math-errno -fschedule-insns2 -fomit-frame-pointer -fPIC -fno-common -mpc64 -rdynamic -I"../include" -o "gsi" _gsi.o _gsi_.o "../lib/libgambit.a" -lutil -ldl -lm -L/usr/local/opt/openssl/lib -lssl -lcrypto libgambitgsi.a ../lib/libgambit.a(os_io.o): In function `___device_tcp_client_close_raw_virt': os_io.c:(.text+0x45e): undefined reference to `SSL_is_init_finished' ../lib/libgambit.a(os_io.o): In function `___os_make_tls_context': os_io.c:(.text+0x22d1): undefined reference to `OPENSSL_init_ssl' os_io.c:(.text+0x22de): undefined reference to `OpenSSL_version_num' os_io.c:(.text+0x2449): undefined reference to `TLS_server_method' os_io.c:(.text+0x2499): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x24d0): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x24e9): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x2502): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x258d): undefined reference to `DH_set0_pqg' os_io.c:(.text+0x25ab): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x25b6): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x25fd): undefined reference to `TLS_client_method' os_io.c:(.text+0x264d): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x2684): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x269d): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x26b6): undefined reference to `SSL_CTX_set_options' os_io.c:(.text+0x27d6): undefined reference to `SSL_CTX_set_options' ../lib/libgambit.a(os_io.o):os_io.c:(.text+0x27eb): more undefined references to `SSL_CTX_set_options' follow collect2: error: ld returned 1 exit status makefile:182: recipe for target 'gsi' failed make[1]: *** [gsi] Error 1 make[1]: Leaving directory '/home/user/tmp/gambit-test/gambit-src/gsi' makefile:467: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 I'm sure there's something simple I'm missing here. Thanks for any recommendations, Bob

1 0

[ANN] Gambit v4.9.0 released
by gambit＠arcade04.iro.umontreal.ca 03 Sep '18

03 Sep '18

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Gambit-list Septembre 2018