David L. BraunThe Brooks Research Group (734) 615-1450
-------- Original message --------From: Reuti <re...@staff.uni-marburg.de>
Date: 9/4/18 6:31 PM (GMT-05:00) To: Open MPI Users
<users@lists.open-mpi.org> Subject: Re: [OMPI users] Are MPI datatypes
guaranteed to be compile-time
constants?
Hi,
Am 04.09.2018 um 23:22 schrieb Benjamin Brock:
> Are M PI datatypes like MPI_INT and MPI_CHAR guaranteed to be compile-time
> constants? Is this defined by the MPI standard, or in the Open MPI
> implementation?
>
> I've written some template code where MPI datatypes are constexpr members,
> which requires that they be known at compile time. This works in Open MPI
> and MPICH, but not in Spectrum MPI--I'm not sure what they've done that
> breaks this, but I'm trying to file a bug and any information you have about
> whether these are compile-time constants would be useful.
For Open MPI and MPICH you can check the definitions with a command like:
$ find . -type f -exec egrep -H ".*define.*MPI_INT.*" {} \;
and get some constants (both *inside* a compiled directory of each, not the
source directories).
What does Spectrum MPI show here? While Platform-MPI was something unique, I
thought Spectrum MPI is based on Open MPI.
How does this effect manifests in Spectrum MPI? It changes between each
compilation of all your source files, i.e. foo.c sees other values than baz.c,
despite the fact that they work together later on when they are linked?
-- Reuti
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
