Dave Goodell wrote:
> Valgrind's "--track-origins=yes" option is usually helpful for
figuring out where the uninitialized values came from.
Good suggestion - that did eventually lead to the solution.
The code always had two vector types (_m128i and _m128), and there are
still two types (_m64
I can't speak to what OMPI might be doing to your program, but I have a few
suggestions for looking into the Valgrind issues.
Valgrind's "--track-origins=yes" option is usually helpful for figuring out
where the uninitialized values came from. However, if I understand you
correctly and if you
> (And yes, as far as I
> can tell it invokes emms before any floating point operations are run
> after each MMX usage.)
Is there anything in Ompi which is likely to cause one of the MMX
routines to be interrupted in such a way that the MMX state is not
saved? The bugs that arise when emms is not
