Re: [eigen] EIGEN_INITIALIZE_MATRICES_BY_NAN?

[ Thread Index | Date Index | More lists.tuxfamily.org/eigen Archives ]


Is valgrind not enough to detect use of uninitialized values?

In my opinion we already have too many compilation options that
changes the behavior of Eigen, and I'd like to keep their number to a
minimum.

gael

On Thu, Apr 19, 2012 at 9:37 PM, Radu B. Rusu <radu.b.rusu@xxxxxxxxx> wrote:
> +1. That looks like a useful feature.
>
> Cheers,
> Radu.
>
>
> On 04/19/2012 12:35 PM, Rhys Ulerich wrote:
>>
>> Any thoughts on having an option like
>> EIGEN_INITIALIZE_MATRICES_BY_ZERO called
>> EIGEN_INITIALIZE_MATRICES_BY_NAN which does what it suggests?  It'd be
>> handy for tracking down algorithmic problems due to uninitialized data
>> being used.  Only hiccups I can see would be initializing the real-
>> and imaginary portion when NumTraits<Scalar>::IsComplex holds and/or
>> using numeric_limits<NumTraits<Scalar>::Real>::has_quiet_NaN to
>> determine when it could be performed at all.
>>
>> - Rhys
>>
>>
>
>



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/