Poly/ML

polyml@lists.polyml.org

695 discussions

5.6 failures on OSX
by Michael.Norrish＠nicta.com.au 08 Jan '16

08 Jan '16

Our regression testing from poly's master branch with sources that are fine on 5.5.2 is showing repeated "random" failures on OSX. You can see the build history at https://travis-ci.org/HOL-Theorem-Prover/HOL/builds (ignore the k11-release-prep branch failures). In all of the recent failures of HOL's master, you'll see that it is the "GITPOLY" build on OSX failing. The GITPOLY build on Linux is fine. Unfortunately, the failures are happening at different times in the build. The only thing they seem to have in common is that there is a test (using OS.Process.isSuccess) of the result of another execution ultimately set up with OS.Process.system. The output even somewhat suggests that the child process terminated successfully; could it be that the return code is being randomly mis-interpreted? Michael ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

2 2

polyml mailing list not searchable by search engines
by artella.coding＠googlemail.com 28 Dec '15

28 Dec '15

For example : https://encrypted.google.com/search?as_q=&as_sitesearch=http%3A%2F%2Flists.… I personally think it would be better to have the mailing list searchable, either by allowing search engines to have access or having a built in site search. Thanks

1 0

Various changes
by David.Matthews＠prolingua.co.uk 20 Nov '15

20 Nov '15

There have been a number of changes added to the git repository over the last weeks and months. This an almost certainly incomplete list. I've tried to include changes that have come up as queries on the mailing list. Added loadHierarchy to PolyML.SavedState. This takes a list of the file names of saved states in order from grandparent, parent to child, and loads them. It functions the same way as loadState except that it allows the parent paths to be specified. Types in structures with opaque signatures are now printed as "?" rather than the print function being inherited. In the debugger, pressing control-C to the debug> prompt returns to the top-level. Actually, what happens is that break-points are disabled and the Thread.Thread.Interrupt exception is raised in the debuggee so it has a chance to clear up. If the debuggee actually catches the interrupt exception then it may not actually return to the top level. There's also a "locals" function in PolyML.Debug to display the local variables. When compiling a file with "use", PolyML.getUseFileName returns the current file name. The floating point precision is now set to 64-bits to avoid inconsistencies depending on whether an intermediate floating point value has been kept in a register or saved into memory. The PolyML.NameSpace structure has been reorganised to split out functions related to the various binding classes into separate sub-structures. The aim is to wrap up the current changes into a new release, probably 5.6 rather than 5.5.3 since there are quite a few changes. That will probably be over the next month or two. David

2 1

loadModule
by David.Matthews＠prolingua.co.uk 10 Nov '15

10 Nov '15

Some new functions have been added to PolyML.SaveState to support "modules". A module is a collection of bindings, primarily structures, signatures and functors, that can be saved and later reloaded. It's mainly aimed at those packaging up binary distributions since a module can only be reloaded into the same binary that exported it, much as with saved states. PolyML.SavedState.savedModule takes a file name and names of structures, signature and functors, together with an optional "on-start-up" function and writes them out as a package. PolyML.SavedState.loadModule takes a name and loads the module. When the module is loaded the "on-start-up" function is executed and the structures, signatures and functors are added to the top-level name space. The module name can either be a file path if it contains a directory separator e.g. ./foo or it is looked up in the path given by POLYMODPATH. There are lower level functions in SavedState that can be used to include values, type constructors and even infix bindings in a module and to import a module into a name space other than the default top-level. The idea is to provide a way for extensions to be packaged up for Poly/ML. There are a number of features that it might be nice to provide but aren't part of the core system. An example would be the Windows GUI modules but I'm sure there are others. I hope it would also encourage contributions. David

1 0

compressing heap images
by Japheth.Lim＠nicta.com.au 02 Nov '15

02 Nov '15

On 21/10/15, Gerwin Klein wrote: > It turns out that with our collection of large Isabelle sessions that we > run regularly, polyml heap image space is becoming a noticeable problem > for us. > We found another way to solve this problem. Isabelle uses saveState to save heaps. If we use saveChild instead, we get a substantial reduction in heap sizes. However, this makes the saved states less portable because they contain the pathname of the parent. Then loading will fail if the heaps are moved to a different path. Here it would be nice if Poly/ML could use relative paths for the parent, and look them up relative to the child. There are other ways to fix this (e.g. chdir before loadState) but I'd rather get the above behaviour from Poly/ML directly. Any thoughts? Japheth ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

2 4

type real in polyml
by immler＠in.tum.de 30 Oct '15

30 Oct '15

Hi David, Thanks for your answer, I should have subscribed to the polyml mailing list earlier. Using the SSE2 instructions and/or setting the intermediate precision to 64 bit would give a nice and clear semantics to floating point expressions in Poly/ML, so I would be very much looking forward to such a change. Best regards, Fabian > Am 07.10.2015 um 15:56 schrieb David Matthews <David.Matthews at prolingua.co.uk>: > > Hi Fabian, > This was a bit bizarre particularly as when I tried it on Windows there > didn't seem to be a problem. It is a problem with the precision and > when rounding occurs. Poly/ML uses the old x87 floating point unit on > both X86/32 and X86/64. As far as I'm aware all x86/64 machines support > the SSE2 instructions so other compilers use SSE2 instructions on 64-bit > but, by default use the x87 instructions on 32-bit. > > The x87 instructions use 80-bit registers internally and only round to > 64-bits when the registers are stored to double-precision values. The > SSE2 instructions are 64-bit so all the results are the same whether > values are stored to memory or not. The x87 has bits in the control > word that can allow it to compute intermediate results to 80-bit, 64-bit > or 32-bit precision. The question is whether this should be set to > 80-bit or 64-bits? > > Currently Poly/ML sets it to 80-bit precision at the start. As far as > I've been able to ascertain that is what other x86/32 compilers do. The > idea is, I suppose, to compute intermediate results to the best > precision available. It does, though, produce the strange results that > you've encountered. I think the reason for the difference in results is > whether the function can be computed at compile-time or not. > > I'm coming round to the view that it should instead set the FPU to > 64-bits so that intermediate results are the same whether they remain in > the register or are written out to memory and reloaded. It looks as > though the libraries in Visual C set that anyway which is why I only saw > the problem when I tested on Linux. This would also mean that results > would not change when, as I plan, I change to using the SSE2 > instructions on x86/64. > > Best regards, > David > > On 07/10/2015 14:07, Fabian Immler wrote: >> Hi David, >> >> Perhaps I should rephrase my enquiry to: "Do I get any guarantees from the implementation of type real in PolyML"? >> Naively, I would have expected, that every subexpression is evaluated according to the IEEE-754 standard (in double precision). >> >> I skimmed the implementation in libpolyml/reals.cpp, it looks like all intermediate results are stored in and retrieved from memory (real_arg, real_result). Is that sufficient to comply to IEEE-754? I.e., can there not occur "double rounding" (as in [1, section 3.3.1])? Or isn't there the need to use something like FLT_EVAL_METHOD=1 [2,3]? >> >> [1] http://www.springer.com/us/book/9780817647049 >> [2] https://en.wikipedia.org/wiki/C99#IEEE.C2.A0754_floating_point_support >> [3] http://www.cplusplus.com/reference/cfloat/ >> >> Best regards, >> Fabian >> >> >>> Am 07.10.2015 um 12:26 schrieb Fabian Immler <immler at in.tum.de>: >>> >>> Hi David, >>> >>> I noticed some strange behavior when working with type real in PolyML: >>> In the following example, where I have "testres = twosum a", depending on whether I call >>> "testres" or "twosum a" I get different results. >>> >>> If I take the definitions out of the structure Test, the results are the same. They are also the same if e.g. print-statements are inserted in between the assignments to b, s, sb and r. The results are also the same when evaluating inside Isabelle with the debugger turned on. >>> >>> Do you have an idea what is going on there? >>> Is it possible that some intermediate results are kept in higher precision in the FPU? >>> Does the compiler perform some "optimizations" on expressions of type real? >>> >>> Best regards, >>> Fabian >>> >>> >>> structure Test = struct >>> >>> fun one n = (if n = 0 then 100.0 else one (n - 1)); >>> >>> val a : real = one 1; >>> >>> fun twosum a = >>> let >>> val b = 1.0/1243313.0; >>> val s = a + b >>> val sb = s - b >>> val r = s - sb >>> in >>> r >>> end; >>> >>> val testres = twosum a; >>> end; >>> >>> open Test; >>> val a = twosum a >>> val b = testres >>> >>> >>>

2 1

Nested use
by David.Matthews＠prolingua.co.uk 21 Oct '15

21 Oct '15

There's long been an issue with "use" when trying to compile and run files which themselves contain "use". For example if ROOT.ML contains: use "first.ML"; use "second.ML"; The inner calls to "use" are taken relative to whatever the original working directory was set to, which means that ROOT.ML always has to be called with the right directory. It's not possible to call use "/home/david/mydirectory/ROOT.ML"; from an arbitrary directory. I've committed a change to the NestedUse branch which is one possible solution to this. The version of "use" in there records the full path to the parent directory of the file name when a file is "used". If that file then contains a nested call to "use" the file is first checked as previously using the original working directory but if that fails it looks for the name by appending the parent directory to the name given. So in the example above, it would first look for "./first.ML" and only if that does not exist would it look for "/home/david/mydirectory/first.ML". This seems as though it should achieve the desired effect with the minimum change to existing programs but there are other alternatives. For example, should it look first relative to the parent directory? David

3 4

compressing heap images
by Gerwin.Klein＠nicta.com.au 21 Oct '15

21 Oct '15

It turns out that with our collection of large Isabelle sessions that we run regularly, polyml heap image space is becoming a noticeable problem for us. To give an impression, we are now daily generating hundreds of gigabytes of polyml heap images. We do this on SSDs, because they reduce build times significantly. For SSDs, hundreds of gigabytes is still a large percentage of total capacity. Raf noticed recently that simple fast compression such as LZO/liblzo works really well for disk heap images. We?re getting a size reduction to about 27% at speeds of about 400MB/s. Initially I thought we might write a little wrapper that compresses/decompresses as polyml writes/reads these images, but it?s awkward, duplicates path logic etc. Would this be something worthwhile to include directly in the polyml heap dumping process instead? That way it would not just benefit us, but everyone who uses Isabelle and other polyml-based sessions on SSDs. Cheers, Gerwin ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

1 0

Profiling
by David.Matthews＠prolingua.co.uk 15 Oct '15

15 Oct '15

There has been some sort of profiling support in Poly/ML almost since the beginning. I have a feeling that the numbering system used in PolyML.profiling dates back to the old Poly language. There have been some recent changes to add support for yet another profiling mode, an option that profiles the time spent in a function but only for the calling thread, giving a way of separating out the work done in a multi-threaded application. It seemed like a good opportunity to revisit the whole thing. I've moved all aspects of profiling into a new structure PolyML.Profiling and removed the PolyML.profiling switch. The various options are now controlled by a datatype and there is a function "profile" that takes a mode, a function and an argument, runs the function by applying it the argument and prints the profile at the end. datatype profileMode = ProfileTime | ProfileAllocations | ProfileLongIntEmulation | ProfileTimeThisThread val profile = fn: profileMode -> ('a -> 'b) -> 'a -> 'b There are a couple of profiling modes that are a bit different since they print information about the state of the heap as the result of the previous computation. They are intended for use with PolyML.Compiler.allocationProfiling which causes the compiler to add extra information about where cells have been allocated. datatype profileDataMode = ProfileLiveData | ProfileLiveMutableData val profileData = fn: profileDataMode -> unit Finally there are additional versions of the functions that take an extra argument to enable an application (e.g. Isabelle) to capture the output from profiling. They take a function that is called with the unsorted list of counts and names. val profileDataStream = fn: ((int * string) list -> unit) -> profileDataMode -> unit val profileStream = fn: ((int * string) list -> unit) -> profileMode -> ('a -> 'b) -> 'a -> 'b David

1 0

incorrect canonical paths
by ramana＠member.fsf.org 15 Oct '15

15 Oct '15

Hi all, I just built Poly/ML fixes-5.2.2 (687b32704fdaffe013427962238482b786b666a4) fresh on a new machine with the following setup: uname -a Linux lemma 4.0.0-2-amd64 #1 SMP Debian 4.0.8-1 (2015-07-11) x86_64 GNU/Linux Now, if I go to a directory with non-lowercase name, I get a bad result: ramana at lemma:~$ mkdir TEST ramana at lemma:~$ cd TEST ramana at lemma:~/TEST$ poly Poly/ML 5.5.3 Testing > OS.Path.mkCanonical(OS.FileSys.getDir()); val it = "/home/ramana/test": string Why does Poly/ML think it is OK to lowercase filenames on this platform? Cheers, Ramana

2 2

← Newer
1
...
18
19
20
21
22
23
24
...
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