This is all good news, even if nobody will actually use icc. Nice work!
Definitely numerical noise.
> sage: q = RDF.pi()/3
> sage: i = q.cos()
> sage: q - i.arccos()
> -2.220446049250313e-16
>
> Is this supposed to be exact?
>
--
You received this message because you are subscribed to the
Be careful with icc compiler family.
It is relatively frequent to get small differences between gcc and icc
floating (double/float) computations.A specialist of floating point said
that icc build faster programs fro two reasons:
1) Intel knows his processors,
2) they make excessive assumptions on
On Wednesday, June 28, 2017 at 4:42:22 AM UTC+2, François Bissey wrote:
>
> sage: q = RDF.pi()/3
> sage: i = q.cos()
> sage: q - i.arccos()
> -2.220446049250313e-16
>
>
sage: q - RDF(1/2).arccos()
-2.220446049250313e-16
on a gcc-based system. Not sure about relevance.
--
You received this m
On 28/06/17 10:51, François Bissey wrote:
with the peculiar being:
**
File "src/sage/rings/real_double.pyx", line 2296, in
sage.rings.real_double.RealDoubleElement.arccos
Failed example:
i.arccos() == q
Expected:
True
On Tuesday, June 27, 2017 at 10:14:30 PM UTC+12, François Bissey wrote:
>
> Well after realising that in its current state #12426/#22646/#23046
> would at least let me try to build sage with the intel compiler,
> I just did go ahead and got myself an open source license.
>
> On top of the abov
