Poly/ML January 2016

polyml@lists.polyml.org

11 participants
14 discussions

linking polyML modules to C
by dtopham＠gmail.com 09 Nov '18

09 Nov '18

After more experimenting with GUI in SML, I would like to now try calling an SML module from a C program. That way, the GUI could be built using traditional imperative techniques and the program logic could be written in SML. I see how to call a C function from SML, but and not so clear on how to call an SML function from a C program. I want to build code using polyc and then link with a C main program, but could anyone show me a simple example of calling that function and getting its return value? for example, I have defined: fun sum i n f = if i > n then 0.0 else f i + sum (i+1) n f ; fun int2real x = real x ; in linkToC.sml and #include <iostream> #include <fstream> std::ofstream ofs; int main() { std::cout << sum(1,10,int2real) << std::endl; ofs.open("table.dat"); for(int i = 0; i < 20; i++) ofs << i << '\t' << sum(1,i,int2real) << std::endl; } in linkToC.cpp Looking in the polyc script, I thought adding the -c option might allow me to build the object code which I could then link to the sml functions, but it complains about not having a main. Could someone point me in the right direction? Thanks, Dave On Mon, Dec 15, 2014 at 11:44 AM, David Topham <dtopham at gmail.com> wrote: > David, Thank you so much! I really appreciate your help with this. Your > sample below builds fine with polyc on my system (PolyML 5.5.2). I am using > a minimal Linux distribution named TinyCore ( > http://distro.ibiblio.org/tinycorelinux/) which comes with OpenMotif > 2.3.3 It runs in a virtual machine within another computer only taking up > a few hundred MBs! > > I am going to use it to help my students explore Discrete Math next > semester (this textbook uses SML for that purpose: > http://cs.wheaton.edu/~tvandrun/dmfp/). > > I also found a reasonably current project using PolyML and Motif here: > http://www.lemma-one.com/ProofPower/index/ > > ...however it was built on PolyML 4 and has not yet been ported to the > newer version (e.g. depends on PolyML.commit which no longer seems to be > supported). > > Happy Holidays to everyone in the PolyML community! > > -David Topham > > >> Re: GUI Interface (David Matthews) >> >> I've experimented with building a stand-alone executable with Motif and >> succeeded in getting it to work for me using polyc. (It required >> building Poly/ML with --with-x). I took the example from >> http://www.polyml.org/docs/Motif.html and wrapped it up in a function. >> I did find a problem, though. It looks as though the function has to >> suspend itself with something like Posix.Process.pause otherwise nothing >> happens. I seem to recall that the Motif stuff is handled on a separate >> thread to allow the REPL to continue to accept commands. With a >> stand-alone application there isn't a REPL so without the "pause" it >> terminates immediately. >> >> David >> >> open XWindows ; >> open Motif ; >> >> fun main() = >> let >> val shell = >> XtAppInitialise "" "xed" "Editor" [] [XmNwidth 400, XmNheight 400] ; >> >> val main = XmCreateMainWindow shell "main" [] ; >> >> val bar = XmCreateMenuBar main "bar" [] ; >> >> val fileMenu = XmCreateCascadeButton bar "file" [XmNlabelString "File"] ; >> val editMenu = XmCreateCascadeButton bar "edit" [XmNlabelString "Edit"] ; >> val viewMenu = XmCreateCascadeButton bar "view" [XmNlabelString "View"] ; >> val helpMenu = XmCreateCascadeButton bar "help" [XmNlabelString "Help"] ; >> >> val command = XmCreateText main "command" [XmNeditMode >> XmSINGLE_LINE_EDIT] ; >> >> val hscroll = XmCreateScrollBar main "hscroll" [XmNorientation >> XmHORIZONTAL] ; >> val vscroll = XmCreateScrollBar main "vscroll" [XmNorientation >> XmVERTICAL] ; >> >> val work = XmCreateDrawingArea main "work" [] ; >> in >> >> XtManageChildren [fileMenu, editMenu, viewMenu, helpMenu] ; >> XtManageChildren [bar, command, hscroll, vscroll, work] ; >> >> XmMainWindowSetAreas main bar command hscroll vscroll work ; >> >> XtManageChild main ; >> XtRealizeWidget shell; >> Posix.Process.pause() >> end; >> >> >> ------------------------------ >> >> _______________________________________________ >> polyml mailing list >> polyml at inf.ed.ac.uk >> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml >> >> End of polyml Digest, Vol 110, Issue 12 >> *************************************** >> >> -- >> The University of Edinburgh is a charitable body, registered in >> Scotland, with registration number SC005336. >> >>

2 3

Assertion `costMin > userGCRatio' failed
by phil.clayton＠lineone.net 28 Jan '16

28 Jan '16

I am getting the following assertion failure with Poly/ML 5.6: eg_test: heapsizing.cpp:602: bool HeapSizeParameters::getCostAndSize(POLYUNSIGNED&, double&, bool): Assertion `costMin > userGCRatio' failed. To get some timing stats, I was running a test application repeatedly to take an average time. It would appear that the sooner I re-run the application after the previous run has terminated, the more likely the above failure is to occur. There is no failure when I run the test once per second manually. Running the test application in quick succession using the command ./eg_test ; ./eg_test gives the failure every 3 to 4 invocations. Is there more information I can provide? Poly/ML 5.5.2 doesn't exhibit this issue. Phil

2 3

Rounding Mode
by jrtc27＠jrtc27.com 27 Jan '16

27 Jan '16

Hi David (cc?d mailing list back in), Of course "bytes 00 00 00 00 00 followed by 00 00 00/01/02" is meant to be "bytes 00 00 00 00 followed by 00 00 00 00/01/02". Regards, James > On 26 Jan 2016, at 14:13, James Clarke <jrtc27 at jrtc27.com> wrote: > > Hi David, > I initially tried to do something like you did (I had val supported = (setRoundingMode TO_NEAREST; true) handle Fail _ => false or similar, and wrapped the whole thing in one if succeeded let ... in () end else ()), but ran into issues where it was failing on x86; I imagine that was because the compiler was performing the operations on constants at compile-time like you said, as it didn?t seem to be following the rounding mode. > > Yes, when I was making the S/390 port, all the streams had streamNo 0 (bytes 00 00 00 00 00 followed by 00 00 00/01/02), so it thought fd 1 and 2 had closed early, causing polyimport to exit with status code 1 without printing anything. The same thing was happening on big-endian 64-bit PPC. > > Regards, > James > >> On 26 Jan 2016, at 14:05, David Matthews <David.Matthews at prolingua.co.uk> wrote: >> >> Hi James, >> I was trying to separate out the change to the tests from the change to reals.cpp. I don't like the idea of changing the test driver and I'd prefer to alter the test itself to deal correctly with the fact that setRoundingMode may raise an exception. I'm aware that it doesn't do that at the moment and it will need your patch or something like it. >> >> You're right that the change I've made is wrong and will also catch the exception raised in "check". Fixing that has, though, shown up a different bug where the compiler is trying to perform the real operations on constants at compile-time before the rounding mode has been set. That didn't show up when they were all top-level expressions. >> >> On your other patch: Was there an issue with the "streamNo" that caused you to make that change? I can see the possibility that unsigned might be different from POLYUNSIGNED (it certainly is on Windows/X64) and that the effect could be to set the wrong part of a word. I'll have to make some further changes because there are now warnings on Windows/64-bit. >> >> Regards, >> David >> >> On 26/01/2016 12:43, James Clarke wrote: >>> Hi, >>> I notice you committed https://github.com/polyml/polyml/commit/891e8122dcca36f9c2e9eea5a3eca7cf5de…. However, as it stands, on armel the calls do not raise an exception like https://github.com/polyml/polyml/pull/16, which could be misleading for the user, as as far as they are aware setting the mode has succeeded (and getting the mode may return the new mode). Also, unless I?m mistaken, you have effectively just completely disabled that test on every platform, as any failure will be caught. >>> >>> Regards, >>> James >>> >>> >>> >>> _______________________________________________ >>> polyml mailing list >>> polyml at inf.ed.ac.uk >>> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml >>> >

2 3

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

Release of 5.6
by David.Matthews＠prolingua.co.uk 26 Jan '16

26 Jan '16

I've just "released" 5.6 on Github and also on SourceForge. As well as the tar sources for Unix there are installers for 32-bit and 64-bit Windows. Thanks to everyone who contributed. David

2 4

Rounding Mode
by jrtc27＠jrtc27.com 26 Jan '16

26 Jan '16

Hi, I notice you committed https://github.com/polyml/polyml/commit/891e8122dcca36f9c2e9eea5a3eca7cf5de…. However, as it stands, on armel the calls do not raise an exception like https://github.com/polyml/polyml/pull/16, which could be misleading for the user, as as far as they are aware setting the mode has succeeded (and getting the mode may return the new mode). Also, unless I?m mistaken, you have effectively just completely disabled that test on every platform, as any failure will be caught. Regards, James

1 0

Changes to Foreign structure
by David.Matthews＠prolingua.co.uk 24 Jan '16

24 Jan '16

There have been a few changes to the Foreign structure. The callN functions have been renamed as buildCallN and the way functions are passed as arguments has been changed. The reason for the changes is to make clear that the expensive operations are creating the C functions and closures and that calling a C function or passing a constructed closure are comparatively cheap. It is important to call the buildXXX functions at the top-level e.g. in a structure, so that the C function is created once. The old callN functions were curried and it wasn't apparent that the partial application to the conversions was quite different to the application of this to the arguments. For that reason the buildXXX take a tuple. David

3 12

Segmentation Fault When Porting
by jrtc27＠jrtc27.com 21 Jan '16

21 Jan '16

Hi, I?ve been trying to port Poly/ML to mips and IBM?s S/390 (the 64-bit version, often referred to as s390x). For both, I tried just adding an extra case in configure.ac, along with corresponding HOSTARCHITECTURE macros and cases in libpolyml/elfexport.cpp. However, these all seem to segfault when polyimport is run when building (both with 5.5.2 and git commit ee26375, "Merge branch ?PICTest?"). I can?t seem to get a meaningful stack trace out of the mips segfault, but it crashes just after ?Use: basis/Socket.sml? is printed. However, on s390x, it crashes before anything is printed, and valgrind gave me the following (with no errors before this point) when running ee26375?s polyimport: ==16138== Thread 3: ==16138== Invalid read of size 8 ==16138== at 0x489EA50: Offset (globals.h:315) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:344) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:350) ==16138== by 0x489EA50: ConstPtrForCode (globals.h:355) ==16138== by 0x489EA50: buildStackList(TaskData*, PolyWord*, PolyWord*) (run_time.cpp:413) ==16138== by 0x489EC87: exceptionToTraceException(TaskData*, SaveVecEntry*) (run_time.cpp:471) ==16138== by 0x48AC9ED: IntTaskData::SwitchToPoly() (interpret.cpp:877) ==16138== by 0x48ACC33: IntTaskData::EnterPolyCode() (interpret.cpp:1428) ==16138== by 0x489324D: NewThreadFunction(void*) (processes.cpp:1128) ==16138== by 0x48E591D: start_thread (pthread_create.c:335) ==16138== by 0x4C8CEA9: ??? (in /lib/s390x-linux-gnu/libc-2.21.so) ==16138== Address 0xe000000005ab5b38 is not stack'd, malloc'd or (recently) free'd ==16138== ==16138== ==16138== Process terminating with default action of signal 11 (SIGSEGV) ==16138== Access not within mapped region at address 0xE000000005AB5000 ==16138== at 0x489EA50: Offset (globals.h:315) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:344) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:350) ==16138== by 0x489EA50: ConstPtrForCode (globals.h:355) ==16138== by 0x489EA50: buildStackList(TaskData*, PolyWord*, PolyWord*) (run_time.cpp:413) ==16138== by 0x489EC87: exceptionToTraceException(TaskData*, SaveVecEntry*) (run_time.cpp:471) ==16138== by 0x48AC9ED: IntTaskData::SwitchToPoly() (interpret.cpp:877) ==16138== by 0x48ACC33: IntTaskData::EnterPolyCode() (interpret.cpp:1428) ==16138== by 0x489324D: NewThreadFunction(void*) (processes.cpp:1128) ==16138== by 0x48E591D: start_thread (pthread_create.c:335) ==16138== by 0x4C8CEA9: ??? (in /lib/s390x-linux-gnu/libc-2.21.so) ==16138== If you believe this happened as a result of a stack ==16138== overflow in your program's main thread (unlikely but ==16138== possible), you can try to increase the size of the ==16138== main thread stack using the --main-stacksize= flag. ==16138== The main thread stack size used in this run was 8388608. (the ??? for libc is because valgrind does not yet understand compressed debug info; I removed a whole load of warnings to that effect) Have you ever come across anything like this? Do you have any thoughts for where to start with hunting this down? Regards, James Clarke

2 11

Foreign calls not working after loadState in new session
by phil.clayton＠lineone.net 19 Jan '16

19 Jan '16

After loading an existing state in a fresh session, I find that previously defined calls to C functions (saved in the state) crash the session if (and only if) the foreign call was called in an earlier session before the state was saved. I can supply an example if necessary. After investigating, it is actually malloc that is failing in the calls. Surprisingly, the very first malloc in the session finds an existing address. As freeList is emptied by PolyML.onEntry presumably freeList is being restored by loadState. Does that sound like an issue? I would expect that the freeList state is untouched by loadState. Phil

2 3

Negative offset for getX and setX functions in Foreign.Memory
by phil.clayton＠lineone.net 18 Jan '16

18 Jan '16

The functions getX and setX in Foreign.Memory take an offset as a Word.word. I'm finding that it is possible to have a negative offset by negating the word offset, e.g. get8 (p, ~ 0w1) Is that guaranteed work generally? Given that Word.wordSize = 63 SysWord.wordSize = 64 I wouldn't have expected this to work for get8/set8 but it does. Phil P.S. My efforts to inspect the source didn't get far as these functions go straight to run-time calls and I'm not familiar with internal representations in Poly/ML...

2 3

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 January 2016