Poly/ML

polyml@lists.polyml.org

695 discussions

fancy tty tricks (with curses?)
by Michael.Norrish＠data61.csiro.au 27 Feb '18

27 Feb '18

Has anyone used the FFI interface or similar to link libcurses or similar? I could try to talk ANSI terminal sequences directly, but querying terminal state with these seems pretty painful. (At the very least one has to put standard input into a non-blocking state?, and I found the Basis documentation on how I might do this very confusing.) And then one is breaking the very abstraction that curses is trying to provide... As a bare minimum for example, I'd like to get the width of the current terminal. Michael

2 1

Poly/ML as alternative to ...
by makarius＠sketis.net 20 Feb '18

20 Feb '18

Dear Poly/ML enthusiasts, quite often the best-known system in a certain category is not really the best. The website https://alternativeto.net occasionally helps to turn perception into reality, by choosing a proper alternative. I have already created entries for some implementations of Standard ML on this site, including https://alternativeto.net/software/poly-ml Maybe some people on this list want to add some more, add likes, comments etc. as a proof that Poly/ML is presently the center of active Standard ML development. Makarius

2 1

build failure on recent Cygwin + Windows 10
by Michael.Norrish＠data61.csiro.au 20 Feb '18

20 Feb '18

../configure seems to work fine, as does much of make, but eventually I get an error where it is trying to make a libtool call involving polyexport.o, and it complains that polyexport.o doesn?t actually exist. Is there something obvious I may be doing wrong? Thanks, Michael

2 2

Poly/ML with libgmp on x86_64-darwin
by makarius＠sketis.net 15 Feb '18

15 Feb '18

Dear Poly/ML enthusiasts and experts of the gcc toolchain on macOS, building Poly/ML with libgmp has always been a challenge, but I have now managed as follows for x86_64-darwin. The approach works as follows: (1) Build libgmp from sources. (2) Build Poly/ML --with-gmp using that homemade version. (3) Copy libgmp.10.dylib into the Poly/ML lib directory and adjust locations with install_name_tool Afterwards it is possible to copy the resulting Poly/ML target directory to a different location on a different machine, with a different (newer) macOS version. The details are in the included build.txt (e.g. for macOS 10.12 Sierra). This is not a shell script! It should be run carefully line-by-line. Towards the end there are two install_name_tool invocations with locations determined beforehand by "otool -L". The final "otool -L" is just a sanity check, the result is like this: target/bin/poly: @executable_path/../lib/libpolyml.9.dylib (compatibility version 10.0.0, current version 10.0.0) @executable_path/../lib/libgmp.10.dylib (compatibility version 14.0.0, current version 14.2.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 307.4.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0) This setup is already part of "isabelle build_polyml", see http://isabelle.in.tum.de/repos/isabelle/file/8b19a8a7f029/src/Pure/Admin/b… -- but that assumes that libgmp has been installed in a standard place (e.g. /usr/local/lib). I wonder if anybody has managed to build libgmp for x86-darwin (32bit) platform. That platform variant still provides better performance for big applications like Isabelle, because it requires only half the memory. Makarius

5 7

Building portable Poly/ML on Linux
by makarius＠sketis.net 11 Feb '18

11 Feb '18

Dear Poly/ML enthusiasts and experts of the gcc toolchain, we've occasionally discussed the problem of building a "portable" Poly/ML on Linux, such that the resulting directory does not have to be "installed" in a fixed location such as /usr/bin and /usr/lib. Here is my current approach to it, using an "rpath" in the poly executable and the chrpath tool to finalize it (on Ubuntu 16.04.3 LTS): make distclean rm -rf target ./configure --prefix="$PWD/target" LDFLAGS=-Wl,-rpath,_DUMMY_ make compiler && make compiler && make install chrpath -r '$ORIGIN/../lib' target/bin/poly Here is a proof for the result: ldd target/bin/poly linux-vdso.so.1 => (0x00007fffdc799000) libpolyml.so.9 => /home/makarius/lib/polyml/polyml-git/target/bin/../lib/libpolyml.so.9 (0x00007f4b02d98000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f4b029ce000) ... Note that the approach with -rpath,_DUMMY_ and separate chrpath has two main reasons: (1) I did not manage to pass $ORIGIN through LDFLAGS, configure, Makefile etc. unharmed, despite some attempts to escape the $ and some more backslashes. (2) The -Wl,-rpath,_DUMMY_ retains a trace from the original target directory, but chrpath -r resets all that cleanly. I am posting this here for the record, as a solution that works so far, see also http://isabelle.in.tum.de/repos/isabelle/file/8b19a8a7f029/src/Pure/Admin/b… Maybe there are further recommendations for simplification, e.g. smarter LDFLAGS could make the chrpath invocation obsolete (avoiding the requirement to install that tool from a separate Linux package). Makarius

3 5

polyc and libraries
by David.Matthews＠prolingua.co.uk 15 Jan '18

15 Jan '18

The polyc script has been developed mainly to simplify the linking of an exported ML function and in particular to try to capture the libraries that need to be included. I've been having another look at this because of an issue that was reported a while back. Up till now the linking step has included all the libraries that were needed in order to link libpolyml itself. That was extracted by the configure script. It turns out that this is right if libpolyml is compiled as a static library but has a problem if libpolyml is a dynamic library. Object files exported by PolyML.export make reference to external symbols from libpolyml but do not directly reference anything else. If libpolyml is a dynamic library it exports these symbols but all the other dependencies are satisfied by loading the appropriate libraries dynamically. The issue was reported in the Fedora distribution but may also affect other distributions that package up Poly/ML and have separate packages for libraries (e.g. libgmp and libffi) and development packages. They were building libpolyml as a shared library but because polyc included the dependencies of libpolyml itself polyc was including -lgmp -lffi in the link step. This meant that it needed the development versions of these libraries even though they were not actually used. I've now modified the configure script so that polyc only includes the dependent libraries if libpolyml has been built with shared libraries disabled and at the same time changed the default so that it builds a shared library unless --disable-shared is given. Hopefully this hasn't broken anything but I'd appreciate any reports of problems. David

4 11

Assertion failure in scanaddrs
by Ramana.Kumar＠cl.cam.ac.uk 15 Jan '18

15 Jan '18

I got this error building the CakeML regression test ( https://cakeml.org/regression.cgi/job/152): scanaddrs.cpp:218: void ScanAddress::ScanAddressesInRegion(PolyWord*, PolyWord*): Assertion `obj->ContainsNormalLengthWord()' failed. Is this worth further investigation? I presume it's somehow due to high memory pressure, though it'd be nice to be more robust to that with a graceful fail.

2 2

More portable poly compilation
by makarius＠sketis.net 24 Dec '17

24 Dec '17

Dear experts on building and linking C++ applications, according to the blog "Creating portable Linux binaries" http://insanecoding.blogspot.de/2012/07/creating-portable-linux-binaries.ht… the following options could make the poly executable more portable accross different Linux versions: CFLAGS="-static-libgcc -static-libstdc++ -Wl,-Bstatic -lgmp -Wl,-Bdynamic" On the surface this works fine on x86_64-linux (Ubuntu 16.04 LTS), but there is a remaining dependency on libpolyml.so, which itself depends on dynamic gcc and stdc++ libraries. Including "-lpolyml" next to "-lgmp" above does not work, probably because these options also apply to the build process of libpolyml itself. How can I make libpolyml a static part of poly? Alternatively, how can I make libgcc and libstdc++ a static part of libpolyml? Makarius

3 2

C++ standard in use
by matthew.fernandez＠gmail.com 23 Dec '17

23 Dec '17

Hi David et al, While experimenting with some of the recent PolyML commits, I realised the build system doesn?t seem to set any particular C++ standard. I guess this results in the compiler default (e.g. GNU++14 in the latest GCC [0]). Is this intentional? Relatedly, coming up on 2018 it seems like it would be reasonable to require a compiler with C++11 support. I?m not sure how backwards compatible PolyML needs to be these days, but e.g. support for Windows 95/98 has been dropped. I notice some comments in interpreter.cpp that imply whatever is in Debian stable is a lower bound. Moving to C++11 would allow some parts of the code base to be replaced with their C++11 equivalents, reducing the maintenance burden. Some candidates: - Bitmap -> std::vector<bool> - NORETURNFN -> [[noreturn]] - PCondVar -> std::condition_variable - PLock -> std::mutex - PLocker -> std::lock_guard Perhaps this will provide a performance boost as well, but I wouldn?t necessarily count on it. I?d be curious to hear if anyone has strong feelings about this or if any PolyML devs out there are living with a pre-C++11 compiler. Thanks, Matt [0]: https://gcc.gnu.org/onlinedocs/gcc/Standards.html#C_002b_002b-Language

3 6

FFI conversions that are portable across Poly/ML versions
by phil.clayton＠veonix.com 22 Dec '17

22 Dec '17

I am trying to define LargeInt.int conversions for C integer types in terms of those supplied in Foreign in a way that will work with both Poly/ML 5.6 or 5.7. This requires that e.g. - Foreign.cUint64 is used for Poly/ML = 5.6 but - Foreign.cUint64Large is used for Poly/ML >= 5.7 I am thinking of achieving this by having separate SML files for different Poly/ML versions and using the right one as follows: let val version = PolyML.rtsVersion () in PolyML.use ( if version >= 570 then "src-5.7.sml" else if version = 560 then "src-5.6.sml" else raise Fail "unsupported Poly/ML version" ) end Is this a future-proof way to choose based on Poly/ML version? Another option might be to copy the implementation of these conversions from Foreign.sml but that may not be possible - for example I couldn't see how to get the flag bigEndian in an application. Is there a better way altogether with some compiler trickery? Phil

2 1

← Newer
1
...
8
9
10
11
12
13
14
...
70
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Poly/ML