1
1

Make C and Fortran types for MPI sentinels agree in size

Fix the C types for the following:

* MPI_UNWEIGHTED
* MPI_WEIGHTS_EMPTY
* MPI_ARGV_NULL
* MPI_ARGVS_NULL
* MPI_ERRCODES_IGNORE

There is lengthy discussion on
https://github.com/open-mpi/ompi/pull/7210 describing the issue; the
gist of it is that the C and Fortran types for several MPI global
sentenial values should agree (specifically: their sizes must(**)
agree).  We erroneously had several of these array-like sentinel
values be "array-like" values in C.  E.g., MPI_ERRCODES_IGNORE was an
(int *) in C while its corresponding Fortran type was "integer,
dimension(1)".  On a 64 bit platform, this resulted in C expecting the
symbol size to be sizeof(int*)==8 while Fortran expected the symbol
size to be sizeof(INTEGER, DIMENSION(1))==4.

That is incorrect -- the corresponding C type needed to be (int).
Then both C and Fortran expect the size of the symbol to be the same.

(**) NOTE: This code has been wrong for years.  This mismatch of types
typically worked because, due to Fortran's call-by-reference
semantics, Open MPI was comparing the *addresses* of these instances,
not their *types* (or sizes) -- so even if C expected the size of the
symbol to be X and Fortran expected the size of the symbol to be Y
(where X!=Y), all we really checked at run time was that the addresses
of the symbols were the same.  But it caused linker warning messages,
and even caused errors in some cases.

Specifically: due to a GNU ld bug
(https://sourceware.org/bugzilla/show_bug.cgi?id=25236), the 5 common
symbols are incorrectly versioned VER_NDX_LOCAL because their
definitions in Fortran sources have smaller st_size than those in
libmpi.so.

This makes the Fortran library not linkable with lld in distributions
that ship openmpi built with -Wl,--version-script
(https://bugs.llvm.org/show_bug.cgi?id=43748):

  % mpifort -fuse-ld=lld /dev/null
  ld.lld: error: corrupt input file: version definition index 0 for symbol
  mpi_fortran_argv_null_ is out of bounds
  >>> defined in /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_usempif08.so
  ...

If we fix the C and Fortran symbols to actually be the same size, the
problem goes away and the GNU ld bug does not come into play.

This commit also fixes a minor issue that MPI_UNWEIGHTED and
MPI_WEIGHTS_EMPTY were not declared as Fortran arrays (not fully fixed
by commit 107c0073dd11fb90d18122c521686f692a32cdd8).

Fixes open-mpi/ompi#7209

Signed-off-by: Fangrui Song <i@maskray.me>
Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
Этот коммит содержится в:
Fangrui Song 2019-11-30 16:56:45 -08:00 коммит произвёл Jeff Squyres
родитель 48c04cd637
Коммит 5609268e90

Просмотреть файл

@ -2,7 +2,7 @@
#
# Copyright (c) 2015 Research Organization for Information Science
# and Technology (RIST). All rights reserved.
# Copyright (c) 2015 Cisco Systems, Inc. All rights reserved.
# Copyright (c) 2015-2020 Cisco Systems, Inc. All rights reserved.
# $COPYRIGHT$
#
# Subroutine to generate a bunch of Fortran declarations and symbols
@ -62,33 +62,33 @@ $fortran->{in_place} = {
f_name => "MPI_IN_PLACE",
};
$fortran->{unweighted} = {
c_type => "int *",
c_type => "int",
c_name => "mpi_fortran_unweighted",
f_type => "integer",
f_type => "integer, dimension(1)",
f_name => "MPI_UNWEIGHTED",
};
$fortran->{weights_empty} = {
c_type => "int *",
c_type => "int",
c_name => "mpi_fortran_weights_empty",
f_type => "integer",
f_type => "integer, dimension(1)",
f_name => "MPI_WEIGHTS_EMPTY",
};
$fortran->{argv_null} = {
c_type => "char *",
c_type => "char",
c_name => "mpi_fortran_argv_null",
f_type => "character, dimension(1)",
f_name => "MPI_ARGV_NULL",
};
$fortran->{argvs_null} = {
c_type => "char *",
c_type => "char",
c_name => "mpi_fortran_argvs_null",
f_type => "character, dimension(1, 1)",
f_name => "MPI_ARGVS_NULL",
};
$fortran->{errcodes_ignore} = {
c_type => "int *",
c_type => "int",
c_name => "mpi_fortran_errcodes_ignore",
f_type => "integer, dimension(1)",
f_name => "MPI_ERRCODES_IGNORE",