Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mismatching types in MPI_win wrappers (and resulting build problems with MPICH 4.x) #48

Open
aradi opened this issue Jun 30, 2023 · 0 comments
Open

Mismatching types in MPI_win wrappers (and resulting build problems with MPICH 4.x) #48

aradi opened this issue Jun 30, 2023 · 0 comments
Labels
bug

Comments

@aradi
Copy link
Member

aradi commented Jun 30, 2023

Currently, MPIFX can not be built with MPICH 4.x.

Problem

The MPI-window wrappers use the old F90 mpi module (instead of mpi_f08) but type(c_ptr) as argument type for pointers, which is strictly only valid when using mpi_f08.

Possible solution

One would have to upgrade the entire library to use mpi_f08 all over.

Converting the pointer argument types to integer(mpi_address_kind) to be compatible with the f90 mpi module is not a real option, as subsequent c_f_pointer() would not work due to type-mismatch.
@aradi aradi added the bug label Jun 30, 2023
@aradi aradi mentioned this issue Jun 30, 2023
Merged
4 tasks
freebsd-git pushed a commit to freebsd/freebsd-ports that referenced this issue Dec 10, 2023
@thierry-FreeBSD
net/mpifx: upgrade to a recent commit in order to support MPICH-4.x
73c6d89 
mpifx does not build with MPICH-4.x:
see <dftbplus/mpifx#48>.

A fix for this issue has been committed, but nothing has been released yet:
meanwhile I propose the attached patch to a recent tag in order to fix the
error.

Remark: this fix requires mpi_f08.mod, to be installed by MPICH.

PR:		275432
Approved by:	yuri@ 'maintainer)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aradi