This is no solution because it requires non-portable application
programming.
> Beyond that, we can ask that an MPI implementation does not make
> certain C lib calls, if those are not thread safe, so as not to
> conflict with such calls made by user code.
> I have no problem with mandating that an MPI library does not invoke
> malloc, if malloc is not thread-safe.
With this solution the users have no problem, but I can imagine that
vendors and implementors of portable MPI implementations have a problem.
======= ============================================
> Has anybody gone systematically thru a Posix standard doc, to
> figure out what is guaranteed to be thread dafe, and what is not?
Sorry, we have nobody here with this info.
But I hope that someone on this list has more info about this.
Rolf
Rolf Rabenseifner (Computer Center )
Rechenzentrum Universitaet Stuttgart (University of Stuttgart)
Allmandring 30 Phone: ++49 711 6855530
D-70550 Stuttgart 80 FAX: ++49 711 6787626
Germany rabenseifner@rus.uni-stuttgart.de