Poly/ML

polyml@lists.polyml.org

695 discussions

structure/signature matching regression in SVN
by fluet＠tti-c.org 09 Apr '09

09 Apr '09

>From recent SVN commit messages, I see that there has been some reorganization of structure/signature matching; apologies if the reorganization is incomplete (i.e., not ready for testing) and/or the following is a known issue. This program type checks under PolyML 5.2.1 (and SML/NJ 110.68 and MLton 20070826), but reports type errors under PolyML SVN HEAD. ===== signature UNIQUE_SET_STRUCTS = sig structure Element: sig type t end end signature UNIQUE_SET = sig include UNIQUE_SET_STRUCTS type t val toList: t -> Element.t list end structure UniqueSetRep = struct datatype 'a t = T of {elements: 'a list} end functor UniqueSet (S: UNIQUE_SET_STRUCTS): UNIQUE_SET = struct open S type elements = Element.t list structure Tree: sig structure Set: sig type t val toList: t -> elements end end = struct structure Set = struct open UniqueSetRep type t = Element.t t fun new elements = T {elements = elements} fun elements (T {elements, ...}) = elements val toList = elements end end open Tree.Set end =====

3 3

Segmentation fault when saving state
by pclayton＠taz.qinetiq.com 03 Apr '09

03 Apr '09

David, We have noticed some interesting behaviour with the state saving in Poly/ML 5.2/5.2.1--- possibly a sign that something isn't quite as intended. If poly is started and the command PolyML.SaveState.saveState "test"; is repeatedly entered, a segmentation fault eventually occurs. On my machine it always happens after 22 times. With the debug level set to 2 or 3, we get: Bad pointer 0x0d479050 found Aborted If we enter PolyML.fullGC (); just before the 22nd go, there is no segmentation fault. However, continuing to enter the original save state command results in the exception Exception- SysErr ("Out of Memory", SOME ENOMEM) raised after 8 more goes. We found this example more by chance. We have had a few other repeatable segmentation faults when saving the state but on very large examples and these are hard to reduce down. (They may be related to the above issue.) In each case, the segmentation fault could be avoided by executing PolyML.fullGC first. Generally, if we cannot create an SML script that generates an error, what is the best way to track down an issue? Thanks, Phil The information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). The information in this communication may be confidential and/or legally privileged. Nothing in this e-mail is intended to conclude a contract on behalf of QinetiQ or make QinetiQ subject to any other legally binding commitments, unless the e-mail contains an express statement to the contrary or incorporates a formal Purchase Order. For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful. Emails and other electronic communication with QinetiQ may be monitored and recorded for business purposes including security, audit and archival purposes. Any response to this email indicates consent to this. Telephone calls to QinetiQ may be monitored or recorded for quality control, security and other business purposes. QinetiQ Limited Registered in England & Wales: Company Number:3796233 Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom http://www.qinetiq.com/home/notices/legal.html

2 3

Compilation error on AIX
by David.Matthews＠prolingua.co.uk 24 Mar '09

24 Mar '09

nitralime wrote: > On Mon, Mar 23, 2009 at 6:55 PM, David Matthews < > I don't know how time consuming the implementation of XCOFF support would > be. > Excuse me my naive question: Is there any plan to implement it? None at the moment. It shouldn't be a great deal of work especially if it is a variant of the PE/COFF. Look at the existing XXXexport.cpp files. You'd have to get the detailed specifications of XCOFF. > I am a little bit confused about your answer. > What would it mean if you fix the bug? The bug I've fixed (in SVN) is simply to allow this file to compile. However the effect of that will be to raise an exception when you try to export in native object file format. The Poly/ML Makefile does an export as part of building the "poly" file so the normal build process won't work. There is also a portable export format which is used for the files in the "imports" directory and the "polyimport" program is used to read and execute them. You would have to adapt the "exportPoly" file which is used to compile the basis library so that after the basis library is compiled the complete Poly/ML system is written out in the portable format rather than native object file format. > Do I get after that an interpreted byte code version of PolyML? The issue of machine code or interpreted code is orthogonal to this. For example, i386 machine code may be exported as PE/COFF, ELF or MachO depending on whether the machine is running Windows, Linux or Mac OS X. Regards, David.

1 0

Compilation error on AIX
by nitralime＠googlemail.com 23 Mar '09

23 Mar '09

Hi, I am trying to compile PolyML 5.2.1 on AIX 5L. After executing configure script "./configure --prefix=/usr/local/polyml" and "gmake" I got the following error message: ---------------------------------------------------------------------------------------- .... g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -MT poly_specific.lo -MD -MP -MF .deps/poly_specifi mv -f .deps/poly_specific.Tpo .deps/poly_specific.Plo /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -M porter.cpp g++ -DHAVE_CONFIG_H -I. -I.. -Wall -O3 -MT exporter.lo -MD -MP -MF .deps/exporter.Tpo -c e exporter.cpp: In function 'SaveVecEntry* exportNative(TaskData*, SaveVecEntry*)': *exporter.cpp:429: error: 'EXC_Fail' was not declared in this scope* gmake[2]: *** [exporter.lo] Error 1 gmake[2]: Leaving directory `/tmp/polyml.5.2.1/libpolyml gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/tmp/polyml.5.2.1' gmake: *** [all] Error 2 ---------------------------------------------------------------------------------------- I am using *gcc version 4.2.4* on *AIX 5.3*. Any help is very much appreciated! Best regards, Nik

2 1

Move to Subversion
by David.Matthews＠prolingua.co.uk 23 Mar '09

23 Mar '09

CVS is getting rather old now and most projects seem to have moved on. I've now moved Poly/ML's CVS repository to subversion and taken the opportunity to enable Trac on the SourceForge site. To download the development version you need svn co https://polyml.svn.sourceforge.net/svnroot/polyml/trunk polyml The subversion repository contains all the CVS history so I'll be disabling CVS shortly. There's quite a bit of work going on with the compiler at the moment with a view to providing much better support for development environments. There's work to make this available in Isabelle and Lucas Dixon is looking at a plug-in for jEdit. There'll be more news as we get things properly working. David.

2 2

Universal binaries
by aleks0＠gmail.com 16 Mar '09

16 Mar '09

Anyone had luck (or know where to begin for...) getting poly/ML to export mac universal binary? I guess a more general question is, can poly/ML make *.o files for a different architecture than the one it is running on?

1 0

Installing Poly/ML
by rda＠lemma-one.com 02 Mar '09

02 Mar '09

I have just learnt a few things installing Poly/ML on a Ubuntu 8.04 system freshly built from the Desktop CD: 1) Ubuntu comes out of the CD with 3/4 of a C compiler. You get gcc, but not libc, so you can compile hello-world.c but not link or run it. The configure script notices this. Installing the package libc6-dev fixes it. 2) But, the configure script doesn't seem to check that there is a C++ compiler (perhaps it should???). The output from configure looked OK, but make fell over with an error: ../libtool: line 1281: g++: command not found Installing the package g++ fixes this. 3) But, poly builds and installs but won't run, because Ubuntu is one of those systems that doesn't include /usr/local/lib on the library path, After starting again with "./configure --prefix=/usr", I have a working compiler. Regards, Rob.

2 1

ML compiler
by ldixon＠inf.ed.ac.uk 06 Feb '09

06 Feb '09

Hi PolyML people, I'm interested in trying to shrink the size of my binary/heap file; I have 18604 lines of library code; the first 6922 lines give a 2.6 MB heap; the next 1200 lines on top of this give a 15 MB heap. I then have 7500 lines of program that push the heap up to 138 MB. (on some Linux' this becomes over 200MB!) I'm doing garbage collection before writing the heap (although it sounds like this is now done automatically); and I can't quite tell how I'm getting this rather nasty blow up in heap size. I suspect my use of substructures, I often have things like: signature N1 ... signature N2 = sig structure n1 : N1 ... end functor N2Fun(n1 : N1 and ...) : N2 = struct structure n1 = n1; ... end; structure n1 : N1 = ... structure n2a = functor(n1 : N1 and ...) : N2; structure n2b = functor(n1 : N1 and ...) : N2; is the code for the substructure n1 literally getting copied each time? Even with this I find it hard to imagine how I'd generate 120 MB of machine code from 7500 lines of ML... I noticed some forget functions in the PolyML compiler; is there some clever way to say all I care about is stuff reachable from calling some specified function? suggestions very welcome, best, lucas

3 5

Updates in CVS
by David.Matthews＠prolingua.co.uk 29 Jan '09

29 Jan '09

There have been a couple of updates to the Poly/ML CVS repository recently apart from those already mentioned on the list. They are both in the C++ run-time system. The mechanism for waiting for external events has been improved which mainly affects Windows pipes and processes. In particular Windows.execute is now much faster when reading from a pipe. I noticed some strange warning messages when building Poly/ML on Cygwin on a new machine of the form "Warning: linker path does not have real file for library -lXXX" It turned out that this was as a result of not having installed the "file" package (/usr/bin/file) rather than anything to do with Poly/ML. Installing this fixed the problem so I've added a test in the configure script which checks for the presence of /usr/bin/file when compiling on Cygwin and produces a more explanatory message if it's not there. David

1 0

Incorrect value for IntInf.pow (~1, ~n) for n = 1, 2, 4, 6, 8 etc.
by pclayton＠taz.qinetiq.com 17 Jan '09

17 Jan '09

In my ignorance I wrote my own exponentiation function for infinite integers, only to find IntInf.pow exists in the basis. Anyway, I ran my test cases on IntInf.pow but they didn't all pass... The following tests should be true but return false: val test = IntInf.pow; test (~1, ~1000000) = 1; test (~1, ~8) = 1; test (~1, ~6) = 1; test (~1, ~4) = 1; test (~1, ~2) = 1; test (~1, ~1) = ~1; It looks like Int.quot(j, 2) on line 117 of basis/IntInf.sml should be Int.rem(j, 2) or possibly andb(j, 1) (as in the local function power). Phil The information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). The information in this communication may be confidential and/or legally privileged. Nothing in this e-mail is intended to conclude a contract on behalf of QinetiQ or make QinetiQ subject to any other legally binding commitments, unless the e-mail contains an express statement to the contrary or incorporates a formal Purchase Order. For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful. Emails and other electronic communication with QinetiQ may be monitored and recorded for business purposes including security, audit and archival purposes. Any response to this email indicates consent to this. Telephone calls to QinetiQ may be monitored or recorded for quality control, security and other business purposes. QinetiQ Limited Registered in England & Wales: Company Number:3796233 Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom http://www.qinetiq.com/home/notices/legal.html

2 1

← Newer
1
...
50
51
52
53
54
55
56
...
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