| Re: [eigen] checking for NaN |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: "Radu B. Rusu" <rusu@xxxxxxxxxxxxxxxx>
- Subject: Re: [eigen] checking for NaN
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Thu, 5 Jan 2012 22:40:03 -0500
- Cc: eigen@xxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ui36M02z8guy5tReA0h1GN5xxxEN5iZ7wJhjkvabUyo=; b=aXIEjcWLt2brF5EOnyyAwzgwoXOcI2A6cvlS0ZCoWXrkOeXaOlOJjUpb5wLezK+109 M7QUcPBMuw+DXlNXUfU9A5tV2vq8k5XeOSXNEQclfL2A+90FDhKSJC4QstBEXj5/s042 zv4LqYG19BvMqPeU9kAhk8XiYr0kUyp4mYAkY=
2012/1/5 Radu B. Rusu <rusu@xxxxxxxxxxxxxxxx>:
> Benoit,
>
> You're correct of course, but the articles that I sent explain how the default x == x test is slower than manually
> crafted SSE optimizations. Is the suggestion you had regarding the eigen array operations faster than doing 4 individual
> checks? Is array1 == array2 nothing but for (int i = 0; i < 3; ++i) array1[i] == array2[i],
I checked the source (ArrayCwiseBinaryOps.h:89):
EIGEN_MAKE_CWISE_BINARY_OP(operator==,std::equal_to)
So we're just using std::equal_to, Eigen is not doing vectorization by
itself here.
Sorry I didn't take a look at your link before posting. I don't know
more on this subject, sorry :)
Benoit