1
1
openmpi/ompi/mpi/f77/bindings.h
George Bosilca df13c2810d Undo the last commit related to the Fortran profiling. After spending few hours
pondering about this problem, we came to the conclusion that the best approach
is to keep what we had before (i.e. the original approach).

The main reason for this is being nice with tool developers. In the current
incarnation, they can either catch the Fortran calls or the C calls. If they
provide both, then they will have to figure out how to cope with the double
calls (as your example highlight).

Here is the behavior Open MPI will stick too:
Fortran MPI  -> C MPI
Fortran PMPI -> C MPI

However, the is another possible approach. This might avoid the double calls
while preserving the tool writers friendliness. This possible approach will do:
   Fortran MPI  -> C MPI
   Fortran PMPI -> C PMPI
                     ^
Unfortunately, we will have to heavily modify all files in the Fortran
interface layer in order to support this approach.

This commit was SVN r20079.
2008-12-06 00:35:32 +00:00

63 строки
2.5 KiB
C

/*
* Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
* University Research and Technology
* Corporation. All rights reserved.
* Copyright (c) 2004-2005 The University of Tennessee and The University
* of Tennessee Research Foundation. All rights
* reserved.
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
* University of Stuttgart. All rights reserved.
* Copyright (c) 2004-2005 The Regents of the University of California.
* All rights reserved.
* $COPYRIGHT$
*
* Additional copyrights may follow
*
* $HEADER$
*/
#ifndef OMPI_F77_BINDINGS_H
#define OMPI_F77_BINDINGS_H
#include "ompi_config.h"
#include "mpi.h"
#include "ompi/errhandler/errhandler.h"
#include "ompi/attribute/attribute.h"
#include "ompi/op/op.h"
#include "ompi/request/grequest.h"
/*
* We now build all four fortran bindings and dont care too much about
* which convention (lowercase, underscore, double underscore or
* all uppercase) is supported by the compiler. The policy now is to
* have the mpi_*_f functions be the default symbols and then wrap
* the four signature types around it. The macro below achieves this.
*/
#define OMPI_GENERATE_F77_BINDINGS(upper_case, \
lower_case, \
single_underscore, \
double_underscore, \
wrapper_function, \
signature, \
params) \
void upper_case signature { wrapper_function params; } \
void lower_case signature { wrapper_function params; } \
void single_underscore signature { wrapper_function params; } \
void double_underscore signature { wrapper_function params; }
/*
* We maintain 2 seperate sets of defines and prototypes. This ensures that
* we can build MPI_* bindings or PMPI_* bindings as ad when needed. The
* top-level always builds MPI_* bindings and bottom level will always build
* PMPI_* bindings. This means that top-level includes "src/mpi/interface/f77"
* .h files and lower-level includes "src/mpi/interface/f77/profile" .h files
*
* Both prototypes for all MPI- PMPI functions is moved into prototypes_mpi.h
*/
#include "ompi/mpi/f77/prototypes_mpi.h"
#include "ompi/mpi/f77/fint_2_int.h"
#endif /* OMPI_F77_BINDINGS_H */