<div class="gmail_quote">On Tue, Nov 8, 2011 at 10:09, jean-frederic thebault <span dir="ltr"><<a href="mailto:jean-frederic@thebault-net.com">jean-frederic@thebault-net.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>First of all, thank you for this library.</div>
<div>View years ago, we had mixed our (f77) finite volume code with petsc, and obtained some very interested results (faster calculations, multi-processor issues, ..), with a 4 linux-PC cluster and a myrinet switch, and petsc-2.1.3</div>
<div>Regarding the new PC architecture (multi-threading), the same mixed code apparently is calculating slower each time we increase the number of processors used (processor or core, I'm not sure to use the right word). We thought that time that we should upgrade our petsc library (with petsc-3.1-p8) </div>
</blockquote><div><br></div><div>Please use petsc-3.2</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>to have benefit of the multi-threading architecture. So do we, changing a little bit some stuff (merrely "include" names). We compiled it with mpif77. The fortran-samples of petsc are working just fine. But our code doesn't work. We have tried a lot of different options and tried for view weeks to figure out what is happening, nothing.</div>
</blockquote><div><br></div><div>The calling sequence for MatSetOption() has changed. You are likely calling it incorrectly.</div><div><br></div><div>The compiler tells you about these things in C. Fortran 77 type checking is nonexistant so the compiler doesn't check these things. If you use F90 or later, you can turn on interface definitions to get some rudimentary type checking. Type checking is much better in C.</div>
</div>