Poly/ML

polyml@lists.polyml.org

695 discussions

Release 5.2 issues
by David.Matthews＠prolingua.co.uk 17 Jun '08

17 Jun '08

I've been away for the last week or so since releasing version 5.2 and there have been a few emails about various issues. Rather than deal with each individually I'm responding to all of them together. > I have installed polyml 5.2 (sources) under > MacOSX 10.4.* and 10.5.*. Both times I had > to manually change in the "make install"-step > the attribute of the file install-sh to 755. > Otherwise the make process would refuse to > finish with permission denied message. Maybe > I have been stupid, but it could also be a bug. The version of install-sh in the CVS repository on sourceforge does not have execute permission and I don't believe it's possible to add it to an existing file. I exported from the repository and forgot to set it explicitly before creating the tar file for the version 5.2 release. It only seems to be a problem on certain platforms. I don't generally like changing a distribution once it has been uploaded but I think the easiest way would be for me to upload a new tar file with execute permissions set on install-sh. > The PolyML.get_print_depth function appears to be missing from 5.2. > Should I rework my code to do without it or was this an unintentional > omission? The PolyML structure has been reworked and in particular PolyML.Compiler has changed. In the old persistent storage version (PolyML 4 and earlier) the print depth and similar values were special kinds of references. From version 5 these are just simple references. The reference set by PolyML.print_depth is now in PolyML.Compiler.printDepth so you can define get_print_depth as ! PolyML.Compiler.printDepth. This is used if the compiler is invoked by means of the usual top-level or with "use" but if PolyML.compiler is called with a value passed in with PolyML.Compiler.CPPrintDepth then this is used in place of the reference. > Has there been a change to the semantics of the function Unix.execute? > > Previously, it executed the programme with respect to the current > path. Now, it seems to require an absolute pathname. There were some changes to Unix.execute and while I was doing it I took a closer look at the Basis Library document. This says that the "cmd" argument should name an executable file. Previously the code used "/bin/sh -c" to run the command. It's easy to add this in the call if you want it to search the path. David.

1 0

Release 5.2
by David.Matthews＠prolingua.co.uk 03 Jun '08

03 Jun '08

I've now released version 5.2 on SourceForge. There are no major changes in this release but it contains some updates and bug fixes. I'll update the release notes shortly but these are the major changes. Change to PolyML.compiler to allow more control over parameters and addition of "name space". The current PolyML.compiler has a different type from previously so this will affect code that uses it. Improvement to real numbers on X86 (32 and 64 bit). Fix to a hot-spot in the compiler. This and other changes seem to have speeded up the compiler by about 10%. Improvement to the source-level debugger (i.e. when compiling with PolyML.debug set to true), especially tracing. Addition of weak references. The Weak structure contains functions to create weak references and arrays and a condition variable and associated mutex that is signalled when a weak reference has been deleted by the garbage collector. Changes to handling of signals by the Signal structure. Rather than forking a new thread to process each signal there is a single thread that executes all the signal handlers. This should improve the responsiveness to an asynchronous signals such as SIGINT. The original control-C handler has been removed and the Poly/ML read-eval-print loop now installs a simple handler for control-C that just generates an Interrupt exception. There have been various bug fixes and probably a few other things that I've forgotten. As always, let me know how it goes. David

1 0

Fwd: [polyml] Re: Interactive behaviour and ctrl-c
by David.Matthews＠prolingua.co.uk 31 May '08

31 May '08

Dear Tom, Your example is essentially doing nothing but growing the stack. The stack is held in the heap and whenever the current segment runs out a new, larger, segment is allocated and the current contents of the stack are copied into that. That can result in garbage collection. Both garbage collection and stack copying are non-interruptible so in either case an interrupt will be deferred until the action is complete. The handling of ctrl/C has been improved in the CVS version compared with the 5.1 release but there are still delays if ctrl/C is pressed during a garbage collection. While investigating this I did discover a bug that resulted in the garbage collector saying that there was insufficient space to extend the stack when in fact there was enough. It's likely now that your example would result in a Warning - Stack limit reached - interrupting process message since the stack will probably run out before the ctrl/C is processed. There may be more of a problem with the 64-bit version than the 32-bit version because the maximum size of a stack segment is larger in the 64-bit version so the limitation is likely to be the overall memory rather than the stack size. David Tom Ridge wrote: > Dear David, > > I just tried the following experiment in poly (see below). > > Under mosml, ctrl-c causes an almost instantaneous return to > top-level. Under poly, the time to return seems dependent on the depth > of recursion(!). Does this sound possible? Is there anyway to get poly > to raise the exception to toplevel in a more timely fashion? > > Thanks > > Tom > > ---------- Forwarded message ---------- > From: Tom Ridge <thomas.ridge(a)cl.cam.ac.uk> > Date: 2008/5/23 > Subject: Re: [polyml] Re: Interactive behaviour and ctrl-c > To: Michael Norrish <Michael.Norrish(a)nicta.com.au> > Cc: hol-developers(a)lists.sourceforge.net > > > Dear All, > > I've just tried this simple experiment in poly's top-level: > > --- > > fun f x = 1 + f x; > > f 1; > > (* leave this to run for 10 or 20 seconds *) > > (* type ctrl-c *) > > (* type f to raise an exception *) > > (* now wait while the exception is raised... this takes a while *) > > --- > > So it seems that the slow-ctrl-c behaviour is something to do with > (64bit) poly, and not HOL. Can someone confirm that this *doesn't* > happen under 32bit poly (linux and Mac). >

2 2

Poly/ML syntax for constructors too liberal?
by rda＠lemma-one.com 13 May '08

13 May '08

Poly/ML correctly allows the following binding: val op :: (h, t) = [1, 2, 3, 4]; However it also allows brackets around the constructor: val (op ::) (h, t) = [1, 2, 3, 4]; My reading of the syntax in the definition of Standard ML is that the latter form should not be allowed. Am I right? Regards, Rob.

4 5

Re: Interactive behaviour and ctrl-c
by thomas.ridge＠cl.cam.ac.uk 13 May '08

13 May '08

Just to follow up my previous post, the first problem also appears under mosml. The behaviour would result if the Interrupt exception were being caught during the proof step and not propagated. The tactic I am using is SIMP. Grepping the HOL sources reveals many places where an arbitrary exception is caught and not propagated. This would prevent Interrupts from being propagated. There has also been some effort to ensure that general exceptions are not caught (e.g. HOL_ERR is caught rather than a general exception). Given that there are many potential places in HOL where Interrupt could be caught and not thrown, is there any reason to believe that the HOL code is not wrong in these places? The second problem, where polyml loses the ability to call system functions, remains. T 2008/5/12 Tom Ridge <thomas.ridge(a)cl.cam.ac.uk>: > Dear All, > > I have been using HOL with Scott Owens' new port to polyml. To > interrupt a proof that takes a long time, I hit ctrl-c. I get the > polyml #> prompt straightaway. However, if I type f (raise an > exception) then nothing happens for a long while. This time seems to > increase the longer the interrupted proof step has been running. > > Eventually the system seems to return, but it is not clear whether an > exception has been raised or not. Certainly the goalstate is now > different. On the other hand, the goal state should not result if the > proof step completed (but this is likely some erroneous behaviour at > the HOL level). > > There is another problem though. The HOL/polyml top-level is usable > for cut-and-pasting. However, I can't invoke any commands that involve > system calls, otherwise I get a "Function system failed" message (from > libpolyml/process_env.cpp). This is a problem because the xemacs sml > mode writes commands to a temporary file and "use"s them into the > top-level. > > Does anyone have any ideas what might be causing these two problems? > > Thanks > > Tom >

2 1

timing issue with polyml 5 on windows
by rdharrison2＠hotmail.co.uk 12 May '08

12 May '08

Hi all, = I've been running polyml 5.1 on windows from a C# application as a child pr= ocess, redirecting standard input/output via the startupinfo and am having = a timing performance problem... = I have found that when sending small SML commands to polyml (that take 10s = of milliseconds to execute) the output only comes back after about 500ms. T= his seems to be because threads in polyml on windows wait for 500ms = in Processes::ThreadPauseForIO before re-polling for input. Is this correct= , and if so can I get around this? (looking at the source code suggests I m= ay be able to send polyml a message to kick it into action at the appropria= te time?) = regards, Richard Harrison. = _________________________________________________________________ Be a Hero and Win with Iron Man http://clk.atdmt.com/UKM/go/msnnkmgl0010000009ukm/direct/01/-------------- = next part -------------- An HTML attachment was scrubbed... URL: http://lists.inf.ed.ac.uk/mailman/private/polyml/attachments/20080501/= d1d4d5a7/attachment.html

3 2

Exception- Subscript unexpectedly raised while compiling
by ldixon＠inf.ed.ac.uk 11 May '08

11 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 While compiling a large program I came across the following rather strange error message: Exception- Subscript unexpectedly raised while compiling Exception- Fail "Exception- Subscript unexpectedly raised while compiling" raised After a bit of hacking I managed to reduce it to the following program: (which uses Isabelle's pretty printing library, and which I tested using Isabelle2007) fun foo l s x i = [] @ map (fn (i,s) => Pretty.block [(case x of NONE => Pretty.str "a" | SOME openi => (if (openi = i) then Pretty.str "b" else Pretty.str "c")), Pretty.str "d"]) l; This is running PolyML 5.1... is this a known issue fixed in more recent cvs snapshots? My workaround was to move the case statement into it's own function. Then it compiles ok. cheers, lucas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIIJ7ciUn2r+81A2gRAlswAJ4/zXeHsGEGYlghC5EwGiFoj3ikxACgpl/l ntaCRqc04AreddbBV/2yYZ8= =kQQi -----END PGP SIGNATURE-----

2 1

Building a console PolyML application on windows
by r.harrison＠eris.qinetiq.com 16 Apr '08

16 Apr '08

Hi David, I've been testing PolyML 5.1 on windows and was wondering how I should go about creating a console PolyML application. I've built polyml using Visual Studio 2005 and the Visual Studio 6 workspace. This worked with hardly any problems. Visual studio 2005 converted the .dsp to a solution without any warnings. Building the solution failed however, as two of the custom build commands needed the $(InputPath) variables double-quoting to protect spaces in the filenames. After this the build succeeded and I was able to export a simple function (fib.obj) and link it using: link /OUT:fib.exe /SUBSYSTEM:WINDOWS fib.obj PolyLib.lib PolyMainLib.lib libcmtd.lib This produces a windows executable using your console GUI (using WinMain as entry point which calls PolyWinMain). What I would really like is an executable or DLL I can use from another application. I don't have much experience with windows programming and in particular DDE which you use for the console GUI so I realise I may be asking a silly question. I would be happy with a simple console application with interaction through stdin, stdout and stderr, so my question is - what's the best way of building such an application? Am I right in thinking that the main runtime is entered through polymain() in PolyLib? Could this be exported along with PolyWinMain from PolyLib.dll and a main() stub be provided in PolyMain.lib. (I've noticed that if you call WinMain with a null pointer for the hInstance parameter you get an (apparently working) console application but this is surely a bad idea and unnecessary! ;-)) regards, Richard.

2 1

compilation problem on x86_64/Debian
by vlaja＠ida.liu.se 08 Apr '08

08 Apr '08

Hello, everyone! I have the following problem when I try to compile PolyML: gmake[2]: Entering directory `/home/vlaja/soft/polyml.5.1/libpolyml' /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -MT x86_dep.lo -MD -MP -MF .deps/x86_dep.Tpo -c -o x86_dep.lo x86_dep.cpp g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -MT x86_dep.lo -MD -MP -MF ..deps/x86_dep.Tpo -c x86_dep.cpp -fPIC -DPIC -o .libs/x86_dep.o x86_dep.cpp: In member function `virtual bool X86Dependent::GetPCandSPFromContext(TaskData*, ucontext_t*, PolyWord*&, byte*&)': x86_dep.cpp:769: error: `REG_RIP' undeclared (first use this function) x86_dep.cpp:769: error: (Each undeclared identifier is reported only once for each function it appears in.) x86_dep.cpp:770: error: `REG_RSP' undeclared (first use this function) gmake[2]: *** [x86_dep.lo] Error 1 gmake[2]: Leaving directory `/home/vlaja/soft/polyml.5.1/libpolyml' Additional information about the system: brutalix <308> uname -a Linux brutalix 2.6.8-12-amd64-k8-smp #1 SMP Tue Dec 5 23:23:41 UTC 2006 x86_64 GNU/Linux brutalix <302> gcc --version gcc (GCC) 3.3.5 (Debian 1:3.3.5-13) I suspect that gcc version is too old. In particular, there is no GNU Standard C++ Library v3 installed (that is why I cannot use the pre-compiled version provided with Isabelle). Is that the source of the problem? Thanks for any help, Vlad

1 0

Controlling printing of exceptions.
by rda＠lemma-one.com 26 Mar '08

26 Mar '08

David, I've also sent this to the mailing list in case any other users have comments. If you write your own read-eval-print loop using PolyML.compiler, you may want to treat exceptions raised during the eval stage specially. However you can't currently stop Poly/ML printing out the exception. It seems appropriate to me to use negative values of the error depth control to do this. I get the effect I want with the following patch: --- mlsource/MLCompiler/COMPILER_BODY.ML- 2006-11-06 13:20:50.000000000 +0000 +++ mlsource/MLCompiler/COMPILER_BODY.ML 2008-02-12 13:22:56.000000000 +0000 @@ -641,14 +641,17 @@ val pstream = prettyPrint (77, lexPrint lex); in - ppBeginBlock pstream (3, false); - ppAddString pstream "Exception-"; - ppBreak pstream (1, 0); - VALUEOPS.printStruct (exceptionData, - TYPETREE.exnType, ! errorDepth, pstream, printEnv); - ppBreak pstream (1, 0); - ppAddString pstream "raised"; - ppEndBlock pstream (); + if ! errorDepth >= 0 + then ( + ppBeginBlock pstream (3, false); + ppAddString pstream "Exception- "; + ppBreak pstream (1, 0); + VALUEOPS.printStruct (exceptionData, + TYPETREE.exnType, ! errorDepth, pstream, printEnv); + ppBreak pstream (1, 0); + ppAddString pstream "raised"; + ppEndBlock pstream () + ) else (); (* print out timing info *) printTimes (parseTime,pass2Time,treeTime,codeTime,endRunTime) I note that the error depth also influences syntax-checking and type-checking error messages, but I can't see why anyone would want to suppress those. Regards, Rob.

3 7

← Newer
1
...
53
54
55
56
57
58
59
...
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