<div class="gmail_quote">[moving to petsc-dev]</div><div class="gmail_quote"><br></div><div class="gmail_quote">On Wed, Nov 3, 2010 at 10:54, Barry Smith <span dir="ltr"><<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div id=":2nr">Right, this is very bad. We set the r2 and r3 up front so the compiler won't complain about possible not set values?<br>
</div></blockquote><div><br></div><div>I don't know, you wrote that code. I stripped it out of a local build and I don't get any warnings in optimized mode (with gcc or clang). I think those warnings were a compiler bug, unless you only saw them with-errorchecking=0.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div id=":2nr">
I guess we need to not use PetscMallocN() for structs and values in the structs.</div></blockquote></div><br><div>Maybe, but only if we really need to set r2 up front.</div><div><br></div><div>Jed</div>