------- Comment #5 from jwbates at mac dot com 2009-05-06 06:39 ------- All of the uninitialized memory errors in valgrind appear to occur after I do the computation, when I'm just trying to print the results.
I can convince myself that there's a good chance that the address swap is leaving big chunks of my real data out in the cold, beyond my control. I mean, if all of my data is sitting in my lhs, and that's being used as the rhs, then it won't get touched. And for what it's worth, when I run valgrind on a version compiled with icc, I get no memory errors. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40036