[polyml] Poly/ML package in Debian and Ubuntu
Does anyone know anything about the polyml package in Debian and Ubuntu? It seems that the currently packaged version is still 5.7.1. I've seen a couple of bug reports that have turned out to be issues that have long since been fixed. I'm quite happy to have Poly/ML packaged for distributions but if they get out of date then they become a problem. David ___ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
Re: [polyml] Poly/ML package in Debian and Ubuntu
On 17 Jan 2022, at 21:54, David Matthews wrote: > > Does anyone know anything about the polyml package in Debian and Ubuntu? It > seems that the currently packaged version is still 5.7.1. I've seen a couple > of bug reports that have turned out to be issues that have long since been > fixed. I'm quite happy to have Poly/ML packaged for distributions but if > they get out of date then they become a problem. I’m the maintainer of the package; I uploaded 5.8.1 a while back to experimental but it failed on a few architectures[1] and I never had the time to dig into the issues, or see if they’ve since been fixed in 5.8.2 or 5.9. It also coincided with having a temporary laptop that wasn’t sufficiently powerful to have a meaningful Debian VM installed, but as of a couple of weeks ago that’s changed and I have a Debian VM again (getting back to polyml was one of the things that was on my mind when setting it up). I don’t know when I’ll have a chance to look at updating the package though, my PhD work is keeping me pretty busy, but hopefully an evening or weekend relatively soon. Jess [1] https://buildd.debian.org/status/package.php?p=polyml&suite=experimental ___ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
Re: [polyml] Poly/ML package in Debian and Ubuntu
On 17/01/2022 22:09, Jessica Clarke wrote: On 17 Jan 2022, at 21:54, David Matthews wrote: Does anyone know anything about the polyml package in Debian and Ubuntu? It seems that the currently packaged version is still 5.7.1. I've seen a couple of bug reports that have turned out to be issues that have long since been fixed. I'm quite happy to have Poly/ML packaged for distributions but if they get out of date then they become a problem. I’m the maintainer of the package; I uploaded 5.8.1 a while back to experimental but it failed on a few architectures[1] and I never had the time to dig into the issues, or see if they’ve since been fixed in 5.8.2 or 5.9. It also coincided with having a temporary laptop that wasn’t sufficiently powerful to have a meaningful Debian VM installed, but as of a couple of weeks ago that’s changed and I have a Debian VM again (getting back to polyml was one of the things that was on my mind when setting it up). I don’t know when I’ll have a chance to look at updating the package though, my PhD work is keeping me pretty busy, but hopefully an evening or weekend relatively soon. Jess, Thanks for the quick reply. It would be good to get this up to date if possible. The issues seem to be mainly with 32-bit architectures that use the interpreted version and I think there were some fixes with that. Since 5.9 the interpreter is used during bootstrap on all systems so it gets much more testing than it used to. David ___ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
Re: [polyml] Update to ARM code-generator
I’m getting random SIGSEGVs while building HOL with latest git on an Apple Silicon MacBook Pro. These don’t always occur, but when they do, they have (so far) always been in one of two places. Michael > On 16 Jan 2022, at 10:51 pm, David Matthews > wrote: > > The long-promised update to the ARM code-generator is now in Git master. > This builds on the old version by adding the register allocation strategy > borrowed from the X86 version as well as low-level peephole optimisation. On > my Apple M1 processor it now seems to be faster than X86 code with Rosetta. > > There are still some improvements to be made, particularly with floating > point, but no major changes are anticipated. It includes one optimisation > that isn't present on the X86 at the moment: small tuples are returned in > registers rather than on the stack. > > Please try it and let me know how it goes. > > David > > ___ > polyml mailing list > polyml@inf.ed.ac.uk > https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.inf.ed.ac.uk%2Fmailman%2Flistinfo%2Fpolyml&data=04%7C01%7Cmichael.norrish%40anu.edu.au%7C26fb8f53e88547f71fcb08d9d8e7092e%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637779763804684071%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=iIPqCbidb5lDxeTnWT8Yf5Rzmym1c3JOfm3J3ANhKa4%3D&reserved=0 ___ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
