Hi James, I've applied your pull request. I've included your clean-up since I don't have any strong feelings about it.
As a result of the discussions about the Mips I've just bought a small development board for the Mips, a Ci20 that is essentially a Mips-based Raspberry Pi. In the early 1990s Prolingua had a Mips Decstation and I wrote a code-generator for Poly when Poly/ML was still written in Poly. Unlike the Sparc and x86 code-generators it never made it into the ML version of Poly/ML. It would be nice to resurrect this and at least put a simple Mips code-generator into Poly/ML if it can be done without a lot of work. Maintaining it in the mainline code is probably too much work but it would be nice to have it available somewhere. Regards, David
On 20/01/2016 17:02, James Clarke wrote:
Hi David, Unfortunately the 5.5.2 S/390 build was not successful. It appears the segfault has been fixed, but now polyimport just exits with exit code 1 (via a POLY_SYS_exit instruction in thread 4, so polytemp.txt does get loaded) and doesn?t print anything. I?m now trying the latest master; if that still has the same problem, I will try and find out why it?s exiting.
I have filed https://github.com/polyml/polyml/pull/14 to allow building on mipsel (I was using my own patch I wrote a while ago to add MIPS support and just applied your endian fix when I said it worked). This also includes a bit of a cleanup which is potentially subjective, so if you disagree with any of the changes I will happily change the pull request.
Regards, James
On 19 Jan 2016, at 22:57, James Clarke <jrtc27 at jrtc27.com> wrote:
Hi David, I added the patch (locally) to the Debian 5.5.2 package; it now builds successfully on sid on mips (and still works on mipsel!) and passes the test suite! Thanks for tracking this down; I shall check it still works with the latest master. I?m also waiting on my S/390 5.5.2 build to finish; hopefully the patch fixes that crash too.
Unrelated: I filed https://github.com/polyml/polyml/pull/13 a few days ago; could you please review it? I noticed that my Debian package build script was in fact not running the test suite, and found out this was because it was running the check rule, which does nothing for Poly/ML. While I can override this default behaviour in the package build script, I thought it would be a good idea if Poly/ML followed the convention.
Thanks, James
polyml mailing list polyml at inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml