Hi John, >> [My case] has nothing to do with tracking uninitialized bits etc in floating >> point numbers. In fact if valgrind ignored floating point numbers and >> just executed them natively that would be fine with me. > > What I distill from this is a request for a "FP mode" which checks > loads from memory to FP registers for valid [allocated] addresses > and [un]init bit values, but immediately marks the bits in the register > as all init or all uninit. FP operations track data flow, but again > the result bits are marked all init or all uninit. Stores from FP > registers to memory are checked for valid [allocated] addresses, > and copy the marking of the bits in register to the memory bytes. > FP modes (width, rounding, etc.) and operations never are changed > from user values.
this sounds like a great plan. Best wishes, Duncan. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
