Poly/ML

polyml@lists.polyml.org

2 participants
711 discussions

Segfault when Printing Exception
by tjark.weber＠gmx.de 01 Oct '12

01 Oct '12

Hi, With Poly/ML 5.5.0 Release RTS version: X86_64-5.5.0, the following code causes a segfault on my machine: signature S = sig val e: exn end; structure s : S = struct exception e end; s.e; Best regards, Tjark

1 0

polyml 5.5 Test071.ML => Failed!!
by gienah＠gentoo.org 26 Sep '12

26 Sep '12

Hi, Thanks for your great work on polyml 5.5. I'd like to bump polyml in Gentoo portage, however this one test fails in the test suite: ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-dependency-tracking --with-x --with-gmp --without-portable --with-threads ... make tests ... Test071.ML => Failed!! ... This is 64 bit amd64 (Intel Core i7) Gentoo linux with gcc 4.7.1, no patches applied to polyml 5.5. Thanks, Mark $ emerge --info '=dev-lang/polyml-5.5' Portage 2.1.11.17 (default/linux/amd64/10.0/developer, gcc-4.7.1, glibc-2.15-r2, 3.5.4-gentoo x86_64) ================================================================= System Settings ================================================================= System uname: Linux-3.5.4-gentoo-x86_64-Intel-R-_Core-TM-_i7_CPU_X_940_(a)_2.13GHz-with-gentoo-2.1 Timestamp of tree: Wed, 19 Sep 2012 04:45:01 +0000 app-shells/bash: 4.2_p37 dev-lang/python: 2.7.3-r2, 3.2.3 dev-util/cmake: 2.8.9 dev-util/pkgconfig: 0.27.1 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.9.8.4 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.68 sys-devel/automake: 1.10.3, 1.11.6 sys-devel/binutils: 2.22-r1 sys-devel/gcc: 4.5.3-r2, 4.6.3, 4.7.1 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82-r3 sys-kernel/linux-headers: 3.5 (virtual/os-headers) sys-libs/glibc: 2.15-r2 Repositories: gentoo lisp gentoo-haskell kde-sunset emacs x-portage ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=native -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -march=native -pipe" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="-j8 --ask-enter-invalid --autounmask=n" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-logs collision-protect config-protect-if-modified distlocks ebuild-locks fixlafiles multilib-strict news parallel-fetch protect-owned sandbox sfperms sign splitdebug strict test unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://mirror.internode.on.net/pub/gentoo http://ftp.swin.edu.au/gentoo http://ftp.jaist.ac.jp/pub/Linux/Gentoo/" LANG="en_AU.UTF-8" LDFLAGS="-Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j8" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/var/lib/layman/lisp /var/lib/layman/haskell /var/lib/layman/kde-sunset /var/lib/layman/emacs /usr/local/portage" SYNC="rsync://rsync.au.gentoo.org/gentoo-portage" USE="X a52 aac acl acpi alsa amd64 berkdb bluetooth branding bzip2 cairo cdda cdparanoia cdr cjk cli consolekit corefonts cracklib crypt cups cxx dbus declarative dri dts dvd dvdr emacs emboss encode examples exif fam ffmpeg firefox flac fortran gcj gd gdbm gdu gif ginac gphoto2 gpm gsm gtk hal hoogle hscolour iconv icu ieee1394 imap ipv6 jpeg kde kipi lcms ldap libnotify lm_sensors mad mmx mng modules mp3 mp4 mpeg mplayer mudflap multilib mysql ncurses nls nptl nsplugin nvidia ocaml ocamlopt odbc ogg opengl openmp pam pango pcre pdf phonon plasma png policykit postgres ppds pppd python qt3support qt4 readline scanner sdl session smartcard smp snmp spell sqlite3 sse sse2 ssl startup-notification svg taglib tcpd theora threads tiff truetype type1 udev udisks unicode upower usb v4l2 vim-syntax vorbis wifi wxwidgets x264 xcb xcomposite xft xinerama xml xscreensaver xulrunner xv xvid xvmc zlib zsh-completion" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" PHP_TARGETS="php5-3" PYTHON_TARGETS="python3_2 python2_7" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" USE_PYTHON="2.7" Unset: CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS $

5 9

Re: two poly 5.5 questions
by David.Matthews＠prolingua.co.uk 26 Sep '12

26 Sep '12

On your other question: > Next, a question on CInterface: Is is possible in PolyML to bind an ML > function to a C function found in the current executable (poly), rather > an in a shared library ? This is not essential as I can always build a > shared library that packs the required functions; it would just be > convenient. If you use Poly/ML through the normal shared library mechanism then the executable contains very little more than the exported ML code. The Poly/ML run-time system and everything else is in shared libraries. You can load those shared libraries through the CInterface mechanism and use anything that is exported. That includes functions in libpolyml but bear in mind that this is mostly C++ rather than C and I'm not sure how many of the symbols are exported. If you're looking to use standard C library functions that are also used by the Poly/ML library it may be possible by loading the appropriate library. What this is will vary between operating systems. To be honest I think it would be easiest and most portable to write your own shared library. David

1 0

Fwd: [Sml-basis-discuss] Evolving the SML Basis Library
by David.Matthews＠prolingua.co.uk 24 Sep '12

24 Sep '12

I received this message from John Reppy just now and thought it might be of interest to the Poly/ML list. In general I'm in favour of evolving libraries rather than the language so I'd tend to look favourably on this but I wondered if there were any views from users of Poly/ML. David -------- Original Message -------- Subject: [Sml-basis-discuss] Evolving the SML Basis Library Date: Mon, 24 Sep 2012 08:15:59 -0500 From: John Reppy <jhr(a)cs.uchicago.edu> To: Sml-basis-discuss(a)mailman.cs.uchicago.edu The SML Basis Library specification was finalized and published about eight years ago. I think that it is past time to consider changes. I see these as falling into three groups: 1) incremental additions of operations to existing modules 2) addition of new signatures, structures, and functors 3) changes to the semantics (including APIs) of existing Basis Library modules We need a process to manage these changes; something like the Scheme RFI (http://srfi.schemers.org) approach should work. We can host the proposals and specifications at Chicago. We also need agreement from maintainers of the major SML implementations that they are willing to support the process by implementing the changes. I hope that this message will start a discussion about the process and provoke suggestions for improvements to the Basis Library (I've got my own list of incremental additions that I'll post soon). - John _______________________________________________ Sml-basis-discuss mailing list Sml-basis-discuss(a)mailman.cs.uchicago.edu https://mailman.cs.uchicago.edu/mailman/listinfo/sml-basis-discuss

2 1

Console i/o issue
by lhe＠it.uu.se 22 Sep '12

22 Sep '12

Hi, I've noticed that Poly/ML handles console I/O differently than at least SML/NJ and Moscow ML. When you read from stdIO in the interactive system, reading starts immediately after the end of the ML compiler input: Poly/ML 5.5.0 Release > TextIO.inputLine TextIO.stdIn;Hello. val it = SOME "Hello.\n": string option ...while in SML/NJ and Moscow ML, reading starts with the next input line: Standard ML of New Jersey v110.74 [built: Tue Jan 31 16:23:10 2012] - TextIO.inputLine TextIO.stdIn; Hello. val it = SOME "Hello.\n" : string option This matters especially if you are writing an interactive program which writes prompts to stdOut. Using Poly/ML, the program must do a dummy read to "consume" the rest of the compiler input before writing a prompt. This causes an incompatibility with SML/NJ and Moscow ML. Worse, if you run a stand-alone application of the program built using Poly/ML there is no compiler input to read, so Poly/ML becomes incompatible with itself... I feel that the reasonable behavior is that of SML/NJ and Moscow ML. Is it possible to change this in Poly/ML? Lars-Henrik Lars-Henrik Eriksson, PhD, Senior Lecturer Computing Science, Dept. of Information Technology, Uppsala University, Sweden E-mail: lhe(a)it.uu.se, Web: http://www.it.uu.se/katalog/lhe?lang=en Phone: +46 18 471 10 57, Mobile: +46 705-36 39 16, Fax: +46 18 51 19 25

4 5

Poly/ML 5.5
by David.Matthews＠prolingua.co.uk 21 Sep '12

21 Sep '12

I have finally released Poly/ML 5.5 on the SourceForge site. I still need to finish the release notes and update the Poly/ML web site. The major change is of course the complete rewrite of the storage management with the garbage-collector now parallelised. In testing the GC sharing pass made a dramatic difference to large Isabelle examples. It would be interesting to know if this makes a difference to other examples. Other major changes are: PolyML.shareCommonData has been parallelised and improved. Support for 64-bit under Windows (Visual Studio or mingw). Object files now use standard "text" and "data" areas when exporting. In particular this means that it is no longer necessary to use --segprot on Mac OS X to avoid a bus error. Libffi is used for the foreign-function interface (CInterface structure). In particular this means that the full range of data types are supported on X86/64. Support for native code on PPC and Sparc has been withdrawn. There are quite a few other minor changes and bug fixes. David

7 11

Type inference issue with phantom types
by phil.clayton＠lineone.net 06 Sep '12

06 Sep '12

I have been making use of phantom types (for encoding a single-inheritance class hierarchy) and have encountered a case where code accepted by MLton does not type check with Poly/ML. After investigating, it appears that MLton, Poly/ML and SML/NJ all take different views on what is a valid program! Attached are two small examples with a slight difference where type checking accepts/rejects as follows: test-1.sml test-2.sml MLton 20100608 accept accept Poly/ML 5.4, latest reject accept SML/NJ 110.73 reject reject I don't know which of the above is consistent with the Definition yet. (I would be very glad if test-1 is a legal program though!) Phil

4 12

End of life for native code Sparc and PPC
by David.Matthews＠prolingua.co.uk 05 Sep '12

05 Sep '12

I'm in the final stages of preparing Poly/ML 5.5 for release and making the pre-built compilers for the various architectures. I have decided not to include support for native code on Sparc and PPC. I don't expect anyone will still be using these architectures for real work and the interpreted version should continue to work. David

1 0

Storage management update
by David.Matthews＠prolingua.co.uk 30 Aug '12

30 Aug '12

The version of Poly/ML in SVN is the result of over a year's work on the storage management. I'm currently testing the final phase of that and I'd be interested in feedback. The garbage collector has been almost completely rewritten and is now parallelised. The minor GC is completely different and uses a copying collector rather than the mark-sweep scheme used for major collections. The final phase is the heap sizing strategy. From the user's point of view the main differences are the options that control the heap management. The old --heap, --mutable and --immutable arguments have been removed. In their place are a new set of arguments: --minheap, --maxheap, --gcpercent and --gcthreads. I have retained the -H argument as a synonym for --minheap. The storage management adjusts the heap size within the range --minheap (default 1/8th of the physical memory) to --maxheap (default 100% of the physical memory) to keep the garbage collection overhead close to --gcpercent (default 10%). If it detects paging it may reduce the heap size to try to avoid paging since the effect of paging is to slow the whole execution down quite substantially. In that case the GC overhead will rise above the target. If necessary it may run an extra "sharing" pass in the GC to reduce the heap size. This is a sort of cut-down version of PolyML.shareCommonData. It adds a considerable overhead to the GC so is only run when absolutely necessary but reducing the live data size can allow a program to proceed when it is bumping up against the --maxheap limit or the paging limit. The overall aim is to try to adjust the heap size for optimum performance with a wide range of programs on a wide range of memory sizes. The larger the heap available the less frequent the GC needs to run so the faster the program runs. This holds up to the point that paging sets in. The available memory, though, depends on what else is running on the machine so in general the heap starts off small and grows while watching for paging. If you know how much memory you have available you may get better performance by setting --minheap and --maxheap. The --gcthreads option sets the number of threads to be used for the parallel GC. The default, 0, uses as many threads as there are processors (cores) on the machine. Setting this to 1 makes the GC single-threaded. It's probably best left at the default unless you want to run other programs at the same time on other cores. I have tested the latest version with Isabelle, primarily on 64-bit Linux. The paging avoidance seems to work well and even large examples will run in 2Gbytes. I haven't tested it much on other platforms. I did notice occasional cases of poly being killed by the over-commit manager. This was fixed by increasing the amount of swap space available. I'd be interested in feedback, particularly if there are pathological cases where the performance is significantly worse. David

2 3

From SML/NJ to Poly/ML
by Gael.Mulat＠mathworks.fr 24 Aug '12

24 Aug '12

Hi, I'm developing in SML for years (so with a big number of lines of code, different projects, in-house libraries, ...). The code compiles well in MLton (for production) and in SML/NJ (for dev and debug). I am considering using Poly/ML to benefit of its debugger. I wonder what will be the effort in order to port the code to Poly/ML. I have already found that: - The organization of the code has to be adapted: sources.cm and mlb files have to be rewritten in some equivalent for polyml - Some libraries will be missing (from my first attempt, it seems that smlnj basis is bigger than what is provided in polyml) - Interfaces with C will have to be adapted (among others: does it exist an easy way to have nlffi in polyml?) - Some grammar constructs may not be accepted by polyml. For example: case x of (0 | 1) => true | _ => false; is not accepted in polyml Does someone have such an experience? Are there documents somewhere that give hints? Are there other big tasks to anticipate for this port? Thanks, Gael Mulat.

9 20

← Newer
1
...
33
34
35
36
37
38
39
...
72
Older →

Jump to page:

2026

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