My fault. I misunderstood the text.

PS: I find  MPI_CHAR variables are a little special.  For  MPI_INT like variables, we get their count from *_handle_alloc. When we write them, very likely we don't increase its count. But for MPI_CHAR variables, it is not the case. When you write them, you probably have a longer string to write! 



--Junchao Zhang


On Sat, Feb 8, 2014 at 9:54 AM, Kathryn Mohror <kathryn@llnl.gov> wrote:
Hi Junchao,

I'm not sure what you mean. MPI_CHAR is in the list of types allowed for variables in section 14.3.5.

Kathryn

On Feb 8, 2014, at 4:54 AM, Junchao Zhang <jczhang@mcs.anl.gov> wrote:

When to use MPI_CHAR? I don't find it in the text.
At least, for non-generic pvars, MPI_CHAR is not in the allowed types currently.

--Junchao Zhang

Hi all,

As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments.

Kathryn


_________________________________________________________________
Kathryn Mohror, kathryn@llnl.gov, http://scalability.llnl.gov/
Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA









_______________________________________________
mpiwg-tools mailing list
mpiwg-tools@lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
_______________________________________________
mpiwg-tools mailing list
mpiwg-tools@lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

_________________________________________________________________
Kathryn Mohror, kathryn@llnl.gov, http://scalability.llnl.gov/
Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA









_______________________________________________
mpiwg-tools mailing list
mpiwg-tools@lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools