[petsc-dev] Hijacked MPI calls...

Jed Brown jed at jedbrown.org
Mon Sep 12 21:22:56 CDT 2016


Eric Chamberland <Eric.Chamberland at giref.ulaval.ca> writes:
> - Would you consider doing static_cast<void>( ) as suggested by clang to 
> silence the warnings?

We want valid C so it'll be ((void)petsc_send_ct++,0).  It's annoying,
but I think we should do it.  There will be a ton of places inside
PETSc.

> - Does PETSc lib really wants to count *my* calls to MPI functions?

It's useful information about what happens inside SNESFunctionEval, for
example.  I don't like that it's messing with something that is not in
PETSc's namespace and would collide with any other library trying to do
the same thing.  So by that metric, it's wrong and we should move it to
a private header.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20160912/ebbdbf52/attachment.sig>


More information about the petsc-dev mailing list