MPI_Get_version(3OpenMPI)MPI_Get_version(3OpenMPI)NAME
MPI_Get_version - Returns the version of the standard corresponding to the current implementation.
SYNTAX C Syntax
#include <mpi.h>
int MPI_Get_version(int *version, int *subversion)
Fortran Syntax
INCLUDE 'mpif.h'
MPI_GET_VERSION(VERSION, SUBVERSION, IERROR)
INTEGER VERSION, SUBVERSION, IERROR
C++ Syntax
#include <mpi.h>
void Get_version(int& version, int& subversion)
OUTPUT PARAMETERS
version The major version number of the corresponding standard (integer).
subversion
The minor version number of the corresponding standard (integer).
IERROR Fortran only: Error status (integer).
DESCRIPTION
Since Open MPI is MPI 2.0 compliant, this function will return a version value of 2 and a subversion value of 0 for this release.
NOTE
MPI_Get_version is one of the few functions that can be called before MPI_Init and after MPI_Finalize.
ERRORS
Almost all MPI routines return an error value; C routines as the value of the function and Fortran routines in the last argument. C++ func-
tions do not return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS, then on error the C++ exception mechanism
will be used to throw an MPI:Exception object.
Before the error value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job, except for
I/O function errors. The error handler may be changed with MPI_Comm_set_errhandler; the predefined error handler MPI_ERRORS_RETURN may be
used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error.
Open MPI 1.2 September 2006 MPI_Get_version(3OpenMPI)
Check Out this Related Man Page
MPI_Is_thread_main(3OpenMPI)MPI_Is_thread_main(3OpenMPI)NAME
MPI_Is_thread_main - Determines if thread called MPI_Init
SYNTAX C Syntax
#include <mpi.h>
int MPI_Is_thread_main(int *flag)
Fortran Syntax
INCLUDE 'mpif.h'
MPI_IS_THREAD_MAIN(FLAG, IERROR)
LOGICAL FLAG
INTEGER IERROR
C++ Syntax
#include <mpi.h>
bool MPI::Is_thread_main()
OUTPUT PARAMETERS
flag True if calling thread is main thread (boolean).
IERROR Fortran only: Error status (integer).
DESCRIPTION
MPI_Is_thread_main is called by a thread to find out whether the caller is the main thread (that is, the thread that called MPI_Init or
MPI_Init_thread).
ERRORS
Almost all MPI routines return an error value; C routines as the value of the function and Fortran routines in the last argument. C++ func-
tions do not return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS, then on error the C++ exception mechanism
will be used to throw an MPI:Exception object.
Before the error value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job, except for
I/O function errors. The error handler may be changed with MPI_Comm_set_errhandler; the predefined error handler MPI_ERRORS_RETURN may be
used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error.
See the MPI man page for a full list of MPI error codes.
SEE ALSO
MPI_Init
MPI_Init_thread
Open MPI 1.2 September 2006 MPI_Is_thread_main(3OpenMPI)
I've been trying to build this thing graphserver (Graphserver - Fine Open Source Itineraries) but I'm getting a build error on Mac OS X 1.4.11.
I've tried using subversion and 0.5 release, both report the same problem.
$ sudo ruby install.rb build
Password:
checking for main() in... (0 Replies)
Ok, i've been messing around in debian the past few days, setting up programs like subversion, mysql and logrotate. The purpose of this script is to use subversion to backup the binary logs. It runs in the cron every 2 hours or so (although I can't get my script to run properly atm, which is why... (1 Reply)
We are using subversion as a version control system in our project. We are connecting to client`s sun Solaris box through check point VPN. Client has installed subversion .
We have created repository and add files to it. Now we want to access the same from our windows machine (through... (0 Replies)