Poly/ML September 2013

polyml@lists.polyml.org

8 participants
6 discussions

Inspecting structures
by ramana.kumar＠gmail.com 27 Jan '16

27 Jan '16

Is there a way to look at the contents (i.e. signature) of a structure without opening it? (I suppose you could just open it then call a lot of PolyML.Compiler.forgetXXX, but that's quite tedious) Also, is it possible to retrieve the long path of an identifier in scope? Something that will, for example, take the rev in scope and say that it came from List. Finally, what about searching for an identifier that would come into scope if you opened some structures?

3 5

[Fwd: Re: [polyml] Building Poly/ML on MacOS X 10.6]
by rda＠lemma-one.com 29 Dec '14

29 Dec '14

I wrote: > I am completely baffled. I thought I hada solved all my problems on > MacOS X > 10.6 and was just tidying up, when I had to recompile a 32 bit > version of > Poly/ML to test a tidied up make file. This failed because > PolyML.Compiler.printTypesWithStructureName no longer exists. The same > problem happened when i rebuild a 64 bit version. What has happened? but it was a false alarm: my make file was wrong for other reasons and the absence of PolyML.Compiler.printTypesWithStructureName was not relevant. No doubt there are good reasons why this variable has been withdrawn. Regards, Rob.

3 6

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

Poly/ML 5.5.1
by David.Matthews＠prolingua.co.uk 16 Oct '13

16 Oct '13

I have uploaded the source for Poly/ML 5.5.1 to the SourceForge site so it is now officially released. I still need to create installers for Windows. The release notes at http://www.polyml.org/docs/ReleaseNotes.html give a general overview of the changes over the last year. There have been no big changes which is the reason it's 5.5.1 rather than 5.6. David

7 20

Compiler in SVN
by David.Matthews＠prolingua.co.uk 03 Sep '13

03 Sep '13

There's been quite a lot of work on the intermediate code optimiser since the last release and it's largely been rewritten. The main aim has been to reduce the number of cases where heap storage was allocated for argument tuples or closures. There were a number of bugs that appeared during testing but I'm not aware of anything outstanding. Isabelle2013 and HOL4 both seem to build successfully and there does seem to be some speed-up. I'd like to release this version in the next month or so but I'd like to fix any other bugs that have been introduced. Please try out the SVN version and let me know how it goes. Don't forget that after the configure and make steps you need to run "make compiler" at least once and preferably twice. Otherwise you will still be using the 5.5 compiler. David

6 16

Warning building Poly/ML on Mac OS X
by rda＠lemma-one.com 01 Sep '13

01 Sep '13

I just built Poly/ML from the latest sources in SVN on Mac OS X 10.8.4 and got the following warning: /bin/sh ./libtool --tag=CC --mode=link gcc -DMACOSX -Wall -fno-strict-aliasing -O3 -I../libffi/include -o poly polyexport.o libpolymain/libpolymain.la libpolyml/libpolyml.la -lpthread -lm -ldl -lstdc++ -lgcc libtool: link: gcc -DMACOSX -Wall -fno-strict-aliasing -O3 -I../libffi/include -o poly polyexport.o libpolymain/.libs/libpolymain.a libpolyml/.libs/libpolyml.a -lpthread -lm -ldl -lstdc++ -lgcc ld: warning: could not create compact unwind for _ffi_call_unix64: does not use RBP or RSP based frame ld: warning: PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not allowed in code signed PIE, but used in area1 from polyexport.o. To fix this warning, don't compile with -mdynamic-no-pic or link with -Wl,-no_pie I don't have any problems running Poly/ML after this, but I wondered if it was something that somebody somewhere might care about. Regards, Rob.

1 0

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 September 2013