| Re: [eigen] sse asin implementation |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] sse asin implementation
- From: Christian Mayer <mail@xxxxxxxxxxxxxxxxx>
- Date: Tue, 07 Apr 2009 19:50:23 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :reply-to:user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=IfoOb3xlabrFxW9Uib5Tofj/xSl+p4n/6wh+4vKvTNk=; b=gzwyvNxT6Ez4VwwoBv+7vSeZvpsGQRDbaE4i+0krIA03CwkXdYlgj3nyFEW+z+ISi/ rp3233YKR9nx5RdDKaNfmDFNlLrutJJDJSgF4dhOZS893wYdC27n0d3HNgJQLP9VsfPb FcMG7IjAA8eN2EZsjF7c2k7b9lt+kCTckvOyk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=PK3qWJ6L2n0OPh2bjnuKExx4bHglhM28kp5nJunayylg7Bd/Uvdqx5/nLoLoA4GH/0 tVOhKKPj/GdpgiDtv+a9tnL8P38lUMwshjfHQs5AjnsU00Yxy93HxfRY88A//SquE1e0 aq9tm5yUhqeLX9LZaiS8w+y4l8u8JlM4sfi44=
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
And everyone who knows numerics is using only floats and the extended
precision of doubles only where it gives an advantage (e.g. to iterate
the error away).
Any algorithm that won't work with floats is badly conditioned and
probably won't work with doubles anyway...
Rohit Garg schrieb:
> Actually AFAIK, using more than 64 bits for doubles is _non_ compliant
> with the IEEE spec.
>
> On Tue, Apr 7, 2009 at 7:25 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
>> 2009/4/7 Rohit Garg <rpg.314@xxxxxxxxx>:
>>> Hang on, I thought otherwise. And Gael pointed out that the sqrt_ps
>>> was exact according to IEEE spec, what about add,sub,mul,div?
>> Ah ok, i got that one wrong. A quick google search suggests that SSE
>> is IEEE compliant indeed. What remains true is that SSE is less
>> precise than non-SSE code for double's because in non-SSE the CPU is
>> able to use long double's of 80 bit internally to limit propagation of
>> errors, but I don't know if anything like that applies for floats
>> (since here we're discussing floats).
>>
>> I told you i'm not competent ;)
>> Benoit
>>
>>
>>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEAREIAAYFAknbkl4ACgkQoWM1JLkHou2ocwCdEFk1kRHsB0Ash0rxlxGLSzlW
cLYAniqUvLD8HqfC4JfA8Xcgi52Tw5xs
=jl1f
-----END PGP SIGNATURE-----