Poly/ML

polyml@lists.polyml.org

2 participants
698 discussions

.polyml and poly-stats
by makarius＠sketis.net 02 Jul '14

02 Jul '14

Just a quick question, before I study the Poly/ML sources in detail. What are the conditions under which Poly/ML 5.5.2 creates a directory $HOME/.polyml and puts poly-stats files there? I have recently found by accident that I have hundreds of such files lying around. Maybe I just got some Poly/ML build/run options wrong, such that statistics are enabled accidentally. I am also using PolyML.Statistics.getLocalStats, but shouldn't the shared-memory file be for global stats only? Makarius

5 8

Poly/ML Array.array segmentation fault
by ramana＠member.fsf.org 09 Jun '14

09 Jun '14

This looks like a bug: % poly Poly/ML 5.5.2 Release > Array.array(~12,4); zsh: segmentation fault (core dumped) poly

2 1

Poly/ML 5.5.2 make fails with linker error
by ykt23＠cam.ac.uk 09 Jun '14

09 Jun '14

I've been trying to build polyML 5.5.2 from the SVN trunk and getting a link error: ./configure --enable-shared ... configure: creating ./config.status config.status: creating include/Makefile config.status: creating include/ffi.h config.status: creating Makefile config.status: creating testsuite/Makefile config.status: creating man/Makefile config.status: creating libffi.pc config.status: creating fficonfig.h config.status: linking src/x86/ffitarget.h to include/ffitarget.h config.status: executing buildir commands config.status: skipping top_srcdir/Makefile - not created config.status: executing depfiles commands config.status: executing libtool commands config.status: executing include commands config.status: executing src commands make make all-recursive make[1]: Entering directory `/home/yongkiam/polymltrunk/polyml' ... mv -f .deps/elfexport.Tpo .deps/elfexport.Plo /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -I../libffi/include -MT unix_specific.lo -MD -MP -MF .deps/unix_specific.Tpo -c -o unix_specific.lo unix_specific.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -I../libffi/include -MT unix_specific.lo -MD -MP -MF .deps/unix_specific.Tpo -c unix_specific.cpp -fPIC -DPIC -o .libs/unix_specific.o libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -I../libffi/include -MT unix_specific.lo -MD -MP -MF .deps/unix_specific.Tpo -c unix_specific.cpp -o unix_specific.o >/dev/null 2>&1 mv -f .deps/unix_specific.Tpo .deps/unix_specific.Plo /bin/bash ../libtool --tag=CXX --mode=link g++ -O3 -I../libffi/include -version-info 6:0:0 -o libpolyml.la -rpath /usr/local/lib arb.lo basicio.lo bitmap.lo check_objects.lo diagnostics.lo errors.lo exporter.lo foreign.lo gc.lo gc_check_weak_ref.lo gc_copy_phase.lo gc_mark_phase.lo gc_share_phase.lo gc_update_phase.lo gctaskfarm.lo heapsizing.lo locking.lo memmgr.lo mpoly.lo network.lo objsize.lo osmem.lo pexport.lo poly_specific.lo polystring.lo process_env.lo processes.lo profiling.lo quick_gc.lo realconv.lo reals.lo rts_module.lo run_time.lo save_vec.lo savestate.lo scanaddrs.lo sharedata.lo sighandler.lo statistics.lo timing.lo xwindows.lo x86_dep.lo x86asmtemp.lo elfexport.lo unix_specific.lo ../libffi/libffi_convenience.la -lpthread -lm -ldl -lstdc++ -lgcc_s -lgcc libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbeginS.o .libs/arb.o .libs/basicio.o .libs/bitmap.o .libs/check_objects.o .libs/diagnostics.o .libs/errors.o .libs/exporter.o .libs/foreign.o .libs/gc.o .libs/gc_check_weak_ref.o .libs/gc_copy_phase.o .libs/gc_mark_phase.o .libs/gc_share_phase.o .libs/gc_update_phase.o .libs/gctaskfarm.o .libs/heapsizing.o .libs/locking.o .libs/memmgr.o .libs/mpoly.o .libs/network.o .libs/objsize.o .libs/osmem.o .libs/pexport.o .libs/poly_specific.o .libs/polystring.o .libs/process_env.o .libs/processes.o .libs/profiling.o .libs/quick_gc.o .libs/realconv.o .libs/reals.o .libs/rts_module.o .libs/run_time.o .libs/save_vec.o .libs/savestate.o .libs/scanaddrs.o .libs/sharedata.o .libs/sighandler.o .libs/statistics.o .libs/timing.o .libs/xwindows.o .libs/x86_dep.o .libs/x86asmtemp.o .libs/elfexport.o .libs/unix_specific.o -Wl,--whole-archive ../libffi/.libs/libffi_convenience.a -Wl,--no-whole-archive -lpthread -ldl -lgcc -L/usr/lib/gcc/x86_64-linux-gnu/4.8 -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/4.8/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crtn.o -O3 -Wl,-soname -Wl,libpolyml.so.6 -o .libs/libpolyml.so.6.0.0 /usr/bin/ld: .libs/x86asmtemp.o: relocation R_X86_64_PC32 against symbol `X86AsmSaveStateAndReturn' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status make[2]: *** [libpolyml.la] Error 1 make[2]: Leaving directory `/home/yongkiam/polymltrunk/polyml/libpolyml' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/yongkiam/polymltrunk/polyml' make: *** [all] Error 2

2 1

standard input contains a leading blank line? (5.5.2 with --enable-shared)
by michael.norrish＠nicta.com.au 28 May '14

28 May '14

If the following is foo.ML: fun doit () = let fun recurse i = case TextIO.inputLine TextIO.stdIn of NONE => () | SOME l => (print (Int.toString i ^ ": " ^ l); recurse (i + 1)) in recurse 1 end; PolyML.export("mytest", doit); and I then do $ poly < foo.ML $ cc -o mytest mytest.o -lpolymain -lpolyml $ echo "hello, world" | ./mytest I get 1: 2: hello, world as output. This is with a polyml 5.5.2 just downloaded from Sourceforge and configured with --enable-shared. I'm pretty sure this used to work (a minor feature of the HOL4 build process depended on it). Michael

2 1

Poly on MinGW
by rda＠lemma-one.com 25 May '14

25 May '14

I am trying to understand my options for using Poly/ML on MinGW for building windows applications coded in Standard ML. There is a bug reported in http://sourceforge.net/p/mingw/bugs/2043/ that you have to work around to build Poly/ML with the current MinGW. The work-around is to run configure with CXXFLAGS="-D_GLIBCXX_HAVE_FENV_H=1? in the environment. (I suspect I should also throw -O3 in there too, as I think that setting CXXFLAGS replaces its initial setting of -O3 inside the makefiles. Is that right?) Having got Poly/ML to compile, I found that polyc gives errors like the following when asked to compile a source file: gcc.exe: error: C:/DOCUME~1/rda/LOCALS~1/Temp/polyobj.2724.obj: No such file or directory If I create an object file from the Poly/ML GUI using PolyML.export, polyc will link it. If I understand what is going on correctly, the resulting program is a Windows application that brings up the Poly/ML GUI to provide the standard input, output and error channels, unless it is run with standard input and output connected to pipes, in which case it works like a pipe. I think I may end up having to package the Standard ML parts of my application as a server, with the GUI provided by clients implemented in some other language. Are there any other options? Regards, Rob.

3 7

Run out of store - interrupting threads
by David.Matthews＠prolingua.co.uk 18 May '14

18 May '14

This question arose from something on the isabelle-dev list but I think it's really of general interest. Currently Poly/ML only gives the "Run out of store - interrupting threads" message if it really cannot allocate the required memory after a full GC. This is actually rather unlikely for small cells. Instead as the amount of free space left in the heap gets smaller the GC runs more and more often. The ML code is still making progress but only very slowly. I wonder if there is a case for actually giving up at that point. Is it better to plough on in the hope that the program will complete or is it more helpful to produce a message and allow the user to try with more memory? This situation is most likely to happen if the heap space is restricted either because the address space limit has been reached in 32-bit mode or if the maximum heap has been set too low with --maxheap. David

2 3

Poly/ML 5.5.2 Released
by David.Matthews＠prolingua.co.uk 17 May '14

17 May '14

Since I haven't had any recent bug reports I've uploaded the current SVN snap-shot to SourceForge as version 5.5.2. Most of the changes are bug fixes. One major fix was to the intermediate code optimiser reported back in September. Other changes are the addition of PrettyStringWithWidth and PrettyLineBreak constructors to the PolyML.pretty datatype, Thread.Thread.numPhysicalProcessors to return the number of physical processors and printing ?.t in circumstances where t is bound to a different type. The debugger has been extended to include structures and the arguments to functors. As always, let me know if you find bugs or problems. David

3 9

polyc
by rda＠lemma-one.com 10 May '14

10 May '14

I have a couple of comments and a query about polyc (which seemed particularly attractive on Cygwin, where there seems to be quite a long list of libraries you need to know about if you are going to call the linker directly). The comment is that the help text is a bit misleading as it has more functionality than just compiling and linking a source file, e.g., you can pass it the name of an object file and it will link it with libpolymain and libpolyml. The query relates to the fact that polyc doesn?t do anything with LD_RUN_PATH (or DYLD_LIBRARY_PATH on Mac OS). Am I right in thinking that libpolyml will now always be statically linked so that you no longer to need to tell the dynamic linker where to find it? (For Poly/ML versions 5.5 and earlier the ProofPower makefiles that I am updating used to create an executable that linked libpolyml dynamically.) Regards, Rob.

4 4

Summer School on Advances in Programming Langauges
by eb120＠hw.ac.uk 14 Apr '14

14 Apr '14

Dear all, Find below the call for applications to attend the AiPL'14 Summer School. Apologies for multiple postings. =================================================== 2nd International Summer School on Advances in Programming Languages 19-22 August 2014, Heriot-Watt University, Edinburgh The 2nd International Summer School on Advances in Programming Languages offers four days of insightful lectures and lab sessions on an engaging blend of cutting-edge theoretical and practical techniques delivered by international experts. The topics include type systems and dependent types, novel programming models, and domain-specific languages, among others. The School is primarily intended for postgraduate research students and aims to foster international collaboration, and encourages a dialogue among early career researchers and renowned scientists. Important Dates: Application deadline: 30 April 2014 Notification: 15 May 2014 Speakers: Philip Wadler, University of Edinburgh Jeremy Gibbons, University of Oxford Fritz Henglein, DIKU, University of Copenhagen Rita Loogen, Philipps-Universit?t Marburg Hans Vandierendonck, Queen's University Belfast Jeremy Singer, University of Glasgow Conor McBride, University of Strathclyde Michele Weiland, Edinburgh Parallel Computing Centre Sven-Bodo Scholz, Heriot-Watt University Edinburgh Greg Michaelson, Heriot-Watt University Edinburgh Cost: 550 GBP - residential 350 GBP - no accommodation included Futher information is available at: http://www.macs.hw.ac.uk/~dsg/events/ISS-AiPL-2014/ =================================================== Evgenij on behalf of the AiPL'14 Organising Committee

1 0

Incorrect floating point conversion
by fw＠deneb.enyo.de 24 Mar '14

24 Mar '14

I noticed this: Poly/ML 5.5.1 Development > val a = 0.99999999999999972244424384371086489409208297729492187;; val a = 1.0: real > val b = 0.999999999999999722444243843710864894092082977294921876;; val b = 1.0: real > a < b;; val it = false: bool > a > b;; val it = false: bool So both values are equal according to Poly/ML. But the correct conversion for the first one is (in hexadecimal floating point notation) 0x1.ffffffffffffdp-1, and for the second 0x1.ffffffffffffep-1, so the values should be different.

4 4

← Newer
1
...
25
26
27
28
29
30
31
...
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