|
From: Yeshurun, M. <mei...@in...> - 2005-09-03 05:40:40
|
Hi, =20 In Valgrind 3.0, Memcheck does not complain when the value of an un-initialized floating point variable is copied to another floating point variable. =20 Is this a deliberate change? (If so, the documentation should be updated.) =20 Thanks, =20 Meir=20 |
|
From: Tom H. <to...@co...> - 2005-09-03 06:14:32
|
In message <942...@ha...>
"Yeshurun, Meir" <mei...@in...> wrote:
> In Valgrind 3.0, Memcheck does not complain when the value of an
> un-initialized floating point variable is copied to another floating
> point variable.
Correct. Floating point values are now tracked fully just as integer
values have always been so you will only get a complain when an
undefined value is used in a way that can effect the program behaviour.
> Is this a deliberate change? (If so, the documentation should be
> updated.)
It might not be entirely obvious, but this entry in NEWS covers it:
On the plus side, Vex and hence Memcheck tracks value flow properly
through floating point and vector registers, something the 2.X line
could not do. That means that Memcheck is much more likely to be
usably accurate on vectorised code.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|