[petsc-dev] PetscOptionsBegin etc all use global variables

Jed Brown jedbrown at mcs.anl.gov
Fri Nov 1 23:27:55 CDT 2013


Barry Smith <bsmith at mcs.anl.gov> writes:

>   hence are not thread safe. Is there any decent way to deal with this?

Make those variables thread local?  Or make the database an object
instead of a collection of global variables, in which case it can be
cloned for each thread to access (and manipulate).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131101/e6e60f64/attachment.sig>


More information about the petsc-dev mailing list