Hi, I have a further question to MPI_NO_OP and MPI_{R}Get_accumulate. I assume that origin_count is not significant for MPI_NO_OP (such as origin_datatype) Which count variable defines the number of basic elements to be returned ? (result_count, result_type) or (target_count, target_type) ? Should an error code be returned if the other number is too small ? Hubert ________________________________________ From: [email protected] [[email protected]] on behalf of Pavan Balaji [[email protected]] Sent: Wednesday, December 05, 2012 11:14 PM To: [email protected] Subject: [Mpi3-rma] RMA WG discussion We talked about different items that need to be addressed for (1) MPI-3 Errata (should only be bug fixes, not all small changes), and (2) MPI-3.1. We still need to discuss the below items in a telecon; this is just a basic separation we did based on the WG discussion. MPI-3 Errata ============ 1. Ticket #348 -- one of the examples has a bug in it, which should be fixed. 2. Ticket #350 -- we should state that for MPI_ACCUMULATE with MPI_NO_OP, the MPI implementation is not allowed to throw an error when the origin buffer is NULL. MPI-3.1 ======= 1. Ticket #344 -- Shared memory attribute query. 2. Ticket #346 -- Info keys are not consistent across window creation routines. 3. Ticket #347 -- Info keys are not listed in the appendix. 4. Ticket #349 -- Addition of MPI_Disp_to_aint and MPI_Aint_to_disp. 5. Addition of the MPI_MODE_NOLOAD assertion. RMA slides have info on this. 6. Info argument addition for req_mem_model. RMA slides have info on this. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji _______________________________________________ mpi3-rma mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-rma Click https://www.mailcontrol.com/sr/gHazrfKyo63GX2PQPOmvUkBugPZ!3WFCbdvywdMxQAVvN... to report this email as spam.