* David Matthews:
> ARM64
> There doesn't seem to be any measurable
> difference in speed by using these instructions compared with the ones
> without the memory barriers although the code is slightly longer.
Did you benchmark this on the M1 only, or on other AArch64
implementations as well?
* David Matthews:
> So the s390x is big-endian?
Yes.
> I don't have access to any big-endian hardware but I managed to find
> an image for a big-endian Mips machine under Qemu and confirm that
> there was a problem.
The GCC compile farm has big endian machines, and so does Debian:
* > Dear experts on building and linking C++ applications,
>
> according to the blog "Creating portable Linux binaries"
> http://insanecoding.blogspot.de/2012/07/creating-portable-linux-binaries.html
> the following options could make the poly executable more portable
> accross different Linux
* Matthew Fernandez:
> Full C++11 support arrived in GCC 4.8.1 [1] and Clang 3.3 [2].
C++11 support is still experimental in the 4.8 series.
Feature-complete doesn't mean that it's production-ready.
___
polyml mailing list
polyml@inf.ed.ac.uk
* David Matthews:
So both values are equal according to Poly/ML. But the correct
conversion for the first one is (in hexadecimal floating point
notation) 0x1.dp-1, and for the second
0x1.ep-1, so the values should be different.
Thanks for reporting that. I find
* Phil Clayton:
WIth 5.5, I get:
real 0m0.016s
user 0m0.003s
sys 0m0.010s
With the latest version (SVN rev 1838), I get:
real 0m0.416s
user 0m0.003s
sys 0m0.010s
The ProofPower build runs Poly/ML about 180 times. The results I am seeing
are compatible with an overhead of about
* Jeremy Dawson:
Trying to run polyml I get the following error:
[jer...@home2006 ~]$ poly
poly: error while loading shared libraries: libstdc++.so.5: cannot
open shared object file: No such file or directory
It seems that binary was compiled with the wrong GCC version.
This is odd, because
* Lu Zhao:
I can write a functor with a single type parameter as follows:
functor MyFctr(type t) =
struct
...
end
What is the correct syntax of writing multiple type parameters for a
functor?
functor MyFctor(type t; type u) = struct end
This follows from the definition of spec (page 14
