[Mpi-forum] C++ types inaccessible after #281

Douglas Miller dougmill at us.ibm.com
Tue Jun 26 15:44:24 CDT 2012

Sure, that sounds pretty reasonable. I just wanted to ask whether it seemed
strange to have "std::complex" in there. Seems like (slightly) more than
"ticket-0" to me, but should be a simple proposal to write.

Douglas Miller                  BlueGene Messaging Development
IBM Corp., Rochester, MN USA                     Bldg 030-2 A401
dougmill at us.ibm.com               Douglas Miller/Rochester/IBM

             Jed Brown                                                     
             <jedbrown at mcs.anl                                             
             .gov>                                                      To 
             Sent by:                  Main MPI Forum mailing list         
             mpi-forum-bounces         <mpi-forum at lists.mpi-forum.org>,    
             @lists.mpi-forum.                                          cc 
                                       Re: [Mpi-forum] C++ types           
             06/26/2012 03:08          inaccessible after #281             
             Please respond to                                             
              Main MPI Forum                                               
               mailing list                                                
             <mpi-forum at lists.                                             

On Tue, Jun 26, 2012 at 10:43 AM, Douglas Miller <dougmill at us.ibm.com>
  I think the issue is just that how can a standard that does not specify
  how C++ fits into things (after ticket 281) then go on to define a data
  type in terms of C++ types?

Is there an informal expectation that implementations will continue to
provide an mpicxx wrapper?

I see no reason for anyone to be attached to std::complex (actually, I
think it's very frequently a bad choice), but having *some* way to use
complex types with a predefined (because one-sided cripples non-predefined)
MPI_Op still seems important.

  If there is a need for a C (not C++) complex datatype, that should be a
  new proposal. But that datatype should not, in my opinion, be defined in
  terms of something like std::complex. If a platform does not support
  something like C99 complex types, then it will have to implement complex
  types and ops itself, or be incomplete.

As mentioned earlier, implementations making MPI_C_COMPLEX available
independent of C99 would be sufficient. Otherwise we are stuck defining our
own types for complex, and then can't use one-sided.

Some discussion of work-arounds:
mpi-forum mailing list
mpi-forum at lists.mpi-forum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20120626/d2298c35/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20120626/d2298c35/attachment-0003.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic31753.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20120626/d2298c35/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://lists.mpi-forum.org/pipermail/mpi-forum/attachments/20120626/d2298c35/attachment-0005.gif>

More information about the mpi-forum mailing list