[Mpi-22] #117: Define a new MPI_Count Datatype

Narasimhan, Kannan kannan.narasimhan at [hidden]
Wed Feb 11 13:09:10 CST 2009



Alexander,

Isn't the representation of MPI_Count (#define vs typedef) a choice best left to each MPI implementation? At the standard level, we just mention that it is equivalent to an int in MPI 2.2. I pretty much modelled this after MPI_Offset and MPI_Aint. 

There has been no discussion so far MPI_Count being on long vs unsigned long in MPI 3.0. 

Thanx!
Kannan 

-----Original Message-----
From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Supalov, Alexander
Sent: Wednesday, February 11, 2009 11:00 AM
To: MPI 2.2
Subject: Re: [Mpi-22] #117: Define a new MPI_Count Datatype

Yes. The #define and typedef ways can complement each other. The #define way will actually not change anything once the preprocessor is run - ints will literally be ints, etc. This would be the mildest way of introducing MPI_Count into the code. The typedef will make the code look different, at least syntactically. If it's set to int, it will be almost, but not quite like #define. It it's set to long,it will be what we want to have for 64-bit ints (provided we want signed counts, that is).

By the way, has this signed vs unsigned been discussed in this context?

-----Original Message-----
From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Narasimhan, Kannan
Sent: Wednesday, February 11, 2009 4:58 PM
To: MPI 2.2
Subject: Re: [Mpi-22] #117: Define a new MPI_Count Datatype

The current proposal has a typedef instead of #define. Are there any specific reasons for preferring the pre-processor macro approach? 

Thanx!
Kannan

-----Original Message-----
From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Supalov, Alexander
Sent: Wednesday, February 11, 2009 6:44 AM
To: MPI 2.2
Subject: Re: [Mpi-22] #117: Define a new MPI_Count Datatype

Hi,

Thanks. I added an offline comment regarding the #define trick for MPI-2.2. Has this been addressed?

Best regards.

Alexander 

-----Original Message-----
From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Narasimhan, Kannan
Sent: Wednesday, February 11, 2009 12:54 AM
To: MPI 2.2
Subject: [Mpi-22] #117: Define a new MPI_Count Datatype

I've updated Ticket #117 ( Define a new MPI_Count Datatype ) to address the issues raised at the MPI Forum Meeting. Is there any other concern that is not addressed in this ticket?

Thanx!
Kannan
_______________________________________________
mpi-22 mailing list
mpi-22_at_[hidden]
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

_______________________________________________
mpi-22 mailing list
mpi-22_at_[hidden]
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22

_______________________________________________
mpi-22 mailing list
mpi-22_at_[hidden]
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

_______________________________________________
mpi-22 mailing list
mpi-22_at_[hidden]
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22



More information about the Mpi-22 mailing list