October 2025 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Error in MPI_IRECV
by phani sri 19 Oct '25

19 Oct '25

Thank you very much, adding -std=legacy to gfortrans compiler flags has solved the problem. On Mon, 20 Oct 2025 at 02:32, fistrosan via discuss <discuss(a)mpich.org> wrote: > If Gregor's answer does not solve it try adding -std=legacy to gfortrans > compiler flags. Sent from Proton Mail for Android. -------- Original > Message -------- On Friday, 10/17/25 at 14: 26 Gregor Corbin via discuss > <discuss@ mpich. org> wrote: > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > If Gregor's answer does not solve it try adding -std=legacy to gfortrans > compiler flags. > > > > Sent from Proton Mail > <https://urldefense.us/v3/__https://proton.me/mail/home__;!!G_uCfscf7eWS!dJK…> > for Android. > > > -------- Original Message -------- > On Friday, 10/17/25 at 14:26 Gregor Corbin via discuss <discuss(a)mpich.org> > wrote: > > Hi, > > let me guess: this code uses `include mpif.h` and is compiled with > gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler > flags. > > Explanation: With the include file, there are no explicit interfaces and > the compiler generates an implicit interface from the call to `MPI_IRECV`. > Having two calls with different argument types is an error since some gcc > version (10 IIRC). > > Cheers, > > Gregor Corbin > > > On 17.10.25 13:30, phani sri via discuss wrote: > > Hi all, I am trying to run FLASH4. 8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. Thank > you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > Hi all, I am trying to run FLASH4.8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. > Thank you in advance. > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 633 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:642:23: > > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:717:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:725:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:260:25: > > 260 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:269:25: > > 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:330:25: > > 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:338:25: > > 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_restrict_ec_genorder.F90:310:37: > > > > -- > *Dr. D. P. S. L. Kameswari* > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe:https://urldefense.us/v3/__https://lists.mpich.org/mailman/list… <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…> > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… > -- *Dr. D. P. S. L. Kameswari*

1 0

Re: [mpich-discuss] Error in MPI_IRECV
by fistrosan 19 Oct '25

19 Oct '25

If Gregor's answer does not solve it try adding -std=legacy to gfortrans compiler flags. Sent from [Proton Mail](https://urldefense.us/v3/__https://proton.me/mail/home__;!!G_uCfscf7eWS!dJKfTCTptV3q_0XDUIiQwsCbaMLbK_wpBUXQlGXJt8y6y91CgHIQadcRpG5GNGcfc6H4q7ws1mpT-QJAKUY$ ) for Android. -------- Original Message -------- On Friday, 10/17/25 at 14:26 Gregor Corbin via discuss <discuss(a)mpich.org> wrote: > Hi, > > let me guess: this code uses `include mpif.h` and is compiled with gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler flags. > > Explanation: With the include file, there are no explicit interfaces and the compiler generates an implicit interface from the call to `MPI_IRECV`. Having two calls with different argument types is an error since some gcc version (10 IIRC). > > Cheers, > > Gregor Corbin > > On 17.10.25 13:30, phani sri via discuss wrote: > >> Hi all, I am trying to run FLASH4. 8, where I am getting the following error. Can someone please, suggest to me why this error is coming. Thank you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & >> ZjQcmQRYFpfptBannerStart >> This Message Is From an External Sender >> This message came from outside your organization. >> >> ZjQcmQRYFpfptBannerEnd >> Hi all, I am trying to run FLASH4.8, where I am getting the following error. Can someone please, suggest to me why this error is coming. >> Thank you in advance. >> 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & >> | 2 >> ...... >> 633 | Call MPI_IRECV(buffert(1,i),buf_size, & >> | 1 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). >> amr_migrate_tree_data.F90:642:23: >> >> 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & >> | 2 >> ...... >> 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & >> | 1 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). >> amr_migrate_tree_data.F90:717:23: >> >> 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & >> | 2 >> ...... >> 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & >> | 1 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). >> amr_migrate_tree_data.F90:725:23: >> >> 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & >> | 2 >> ...... >> 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & >> | 1 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). >> amr_migrate_tree_data.F90:260:25: >> >> 260 | Call MPI_IRECV(buffert(1,i),buf_size, & >> | 1 >> ...... >> 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & >> | 2 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). >> amr_migrate_tree_data.F90:269:25: >> >> 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & >> | 1 >> ...... >> 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & >> | 2 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). >> amr_migrate_tree_data.F90:330:25: >> >> 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & >> | 1 >> ...... >> 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & >> | 2 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). >> amr_migrate_tree_data.F90:338:25: >> >> 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & >> | 1 >> ...... >> 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & >> | 2 >> Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). >> amr_restrict_ec_genorder.F90:310:37: >> >> -- >> >> Dr. D. P. S. L. Kameswari >> >> _______________________________________________ >> discuss mailing list >> discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…

1 0

Re: [mpich-discuss] Error in MPI_IRECV
by Jenke, Joachim 18 Oct '25

18 Oct '25

Hi phani sri, I think your assertion is wrong. It looks like the flags fixed your initial issue. The initial error was raised by the compilation step. Now you run into the next issue raised by the linking step (which was never reached in your previous attempts). Please provide more details about the new error messages so that we have a chance to understand your new issue. Best Joachim Am 18.10.2025 06:05 schrieb phani sri via discuss <discuss(a)mpich.org>: Hi Hui, this also did not work. It is ending up with the error: collect2: error: ld returned 1 exit status. On Fri, 17 Oct 2025 at 21: 11, Zhou, Hui <zhouh@ anl. gov> wrote: Hi phani sri, Try set `FFLAGS=-fallow-argument-mismatch` and `FCFLAGS=-fallow-argument-mismatch` ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi Hui, this also did not work.It is ending up with the error: collect2: error: ld returned 1 exit status. On Fri, 17 Oct 2025 at 21:11, Zhou, Hui <zhouh(a)anl.gov<mailto:[email protected]>> wrote: Hi phani sri, Try set `FFLAGS=-fallow-argument-mismatch` and `FCFLAGS=-fallow-argument-mismatch` and let us know if that helps. Hui ________________________________ From: phani sri via discuss <discuss(a)mpich.org<mailto:[email protected]>> Sent: Friday, October 17, 2025 8:07 AM To: discuss(a)mpich.org<mailto:[email protected]> <discuss(a)mpich.org<mailto:[email protected]>> Cc: phani sri <phanisri123(a)gmail.com<mailto:[email protected]>> Subject: Re: [mpich-discuss] Error in MPI_IRECV Hi Gregor, I have checked this, the code is using mpi. h not mpif. h. Dr. D. P. S. L. Kameswari On Fri, 17 Oct 2025, 5: 56 pm Gregor Corbin via discuss, <discuss@ mpich. org> wrote: Hi, let me guess: this code uses `include mpif. h` and is compiled ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi Gregor, I have checked this, the code is using mpi.h not mpif.h. Dr. D. P. S. L. Kameswari On Fri, 17 Oct 2025, 5:56 pm Gregor Corbin via discuss, <discuss(a)mpich.org<mailto:[email protected]>> wrote: Hi, let me guess: this code uses `include mpif.h` and is compiled with gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler flags. Explanation: With the include file, there are no explicit interfaces and the compiler generates an implicit interface from the call to `MPI_IRECV`. Having two calls with different argument types is an error since some gcc version (10 IIRC). Cheers, Gregor Corbin On 17.10.25 13:30, phani sri via discuss wrote: Hi all, I am trying to run FLASH4. 8, where I am getting the following error. Can someone please, suggest to me why this error is coming. Thank you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi all, I am trying to run FLASH4.8, where I am getting the following error. Can someone please, suggest to me why this error is coming. Thank you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 ...... 633 | Call MPI_IRECV(buffert(1,i),buf_size, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:642:23: 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 ...... 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:717:23: 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 ...... 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:725:23: 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 ...... 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:260:25: 260 | Call MPI_IRECV(buffert(1,i),buf_size, & | 1 ...... 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:269:25: 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & | 1 ...... 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:330:25: 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & | 1 ...... 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:338:25: 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & | 1 ...... 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_restrict_ec_genorder.F90:310:37: -- Dr. D. P. S. L. Kameswari _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…> _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…> -- Dr. D. P. S. L. Kameswari

1 0

Re: [mpich-discuss] Error in MPI_IRECV
by phani sri 17 Oct '25

17 Oct '25

Hi Hui, this also did not work.It is ending up with the error: collect2: error: ld returned 1 exit status. On Fri, 17 Oct 2025 at 21:11, Zhou, Hui <zhouh(a)anl.gov> wrote: > Hi phani sri, > > Try set `FFLAGS=-fallow-argument-mismatch` and > `FCFLAGS=-fallow-argument-mismatch` and let us know if that helps. > > Hui > ------------------------------ > *From:* phani sri via discuss <discuss(a)mpich.org> > *Sent:* Friday, October 17, 2025 8:07 AM > *To:* discuss(a)mpich.org <discuss(a)mpich.org> > *Cc:* phani sri <phanisri123(a)gmail.com> > *Subject:* Re: [mpich-discuss] Error in MPI_IRECV > > Hi Gregor, I have checked this, the code is using mpi. h not mpif. h. Dr. > D. P. S. L. Kameswari On Fri, 17 Oct 2025, 5: 56 pm Gregor Corbin via > discuss, <discuss@ mpich. org> wrote: Hi, let me guess: this code uses > `include mpif. h` and is compiled > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > Hi Gregor, I have checked this, the code is using mpi.h not mpif.h. > > *Dr. D. P. S. L. Kameswari* > > > On Fri, 17 Oct 2025, 5:56 pm Gregor Corbin via discuss, <discuss(a)mpich.org> > wrote: > > Hi, > > let me guess: this code uses `include mpif.h` and is compiled with > gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler > flags. > > Explanation: With the include file, there are no explicit interfaces and > the compiler generates an implicit interface from the call to `MPI_IRECV`. > Having two calls with different argument types is an error since some gcc > version (10 IIRC). > > Cheers, > > Gregor Corbin > > > On 17.10.25 13:30, phani sri via discuss wrote: > > Hi all, I am trying to run FLASH4. 8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. Thank > you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > Hi all, I am trying to run FLASH4.8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. > Thank you in advance. > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 633 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:642:23: > > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:717:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:725:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:260:25: > > 260 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:269:25: > > 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:330:25: > > 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:338:25: > > 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_restrict_ec_genorder.F90:310:37: > > > > -- > *Dr. D. P. S. L. Kameswari* > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe:https://urldefense.us/v3/__https://lists.mpich.org/mailman/list… <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…> > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… > <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…> > > -- *Dr. D. P. S. L. Kameswari*

1 0

Re: [mpich-discuss] Error in MPI_IRECV
by Zhou, Hui 17 Oct '25

17 Oct '25

Hi phani sri, Try set `FFLAGS=-fallow-argument-mismatch` and `FCFLAGS=-fallow-argument-mismatch` and let us know if that helps. Hui ________________________________ From: phani sri via discuss <discuss(a)mpich.org> Sent: Friday, October 17, 2025 8:07 AM To: discuss(a)mpich.org <discuss(a)mpich.org> Cc: phani sri <phanisri123(a)gmail.com> Subject: Re: [mpich-discuss] Error in MPI_IRECV Hi Gregor, I have checked this, the code is using mpi. h not mpif. h. Dr. D. P. S. L. Kameswari On Fri, 17 Oct 2025, 5: 56 pm Gregor Corbin via discuss, <discuss@ mpich. org> wrote: Hi, let me guess: this code uses `include mpif. h` and is compiled ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi Gregor, I have checked this, the code is using mpi.h not mpif.h. Dr. D. P. S. L. Kameswari On Fri, 17 Oct 2025, 5:56 pm Gregor Corbin via discuss, <discuss(a)mpich.org<mailto:[email protected]>> wrote: Hi, let me guess: this code uses `include mpif.h` and is compiled with gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler flags. Explanation: With the include file, there are no explicit interfaces and the compiler generates an implicit interface from the call to `MPI_IRECV`. Having two calls with different argument types is an error since some gcc version (10 IIRC). Cheers, Gregor Corbin On 17.10.25 13:30, phani sri via discuss wrote: Hi all, I am trying to run FLASH4. 8, where I am getting the following error. Can someone please, suggest to me why this error is coming. Thank you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi all, I am trying to run FLASH4.8, where I am getting the following error. Can someone please, suggest to me why this error is coming. Thank you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 ...... 633 | Call MPI_IRECV(buffert(1,i),buf_size, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:642:23: 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 ...... 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:717:23: 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 ...... 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:725:23: 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 ...... 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:260:25: 260 | Call MPI_IRECV(buffert(1,i),buf_size, & | 1 ...... 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:269:25: 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & | 1 ...... 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:330:25: 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & | 1 ...... 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:338:25: 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & | 1 ...... 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_restrict_ec_genorder.F90:310:37: -- Dr. D. P. S. L. Kameswari _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…> _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… <https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss…>

1 0

Re: [mpich-discuss] Error in MPI_IRECV
by phani sri 17 Oct '25

17 Oct '25

Hi Gregor, I have checked this, the code is using mpi.h not mpif.h. *Dr. D. P. S. L. Kameswari* On Fri, 17 Oct 2025, 5:56 pm Gregor Corbin via discuss, <discuss(a)mpich.org> wrote: > Hi, > > let me guess: this code uses `include mpif.h` and is compiled with > gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler > flags. > > Explanation: With the include file, there are no explicit interfaces and > the compiler generates an implicit interface from the call to `MPI_IRECV`. > Having two calls with different argument types is an error since some gcc > version (10 IIRC). > > Cheers, > > Gregor Corbin > > > On 17.10.25 13:30, phani sri via discuss wrote: > > Hi all, I am trying to run FLASH4. 8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. Thank > you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > Hi all, I am trying to run FLASH4.8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. > Thank you in advance. > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 633 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:642:23: > > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:717:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:725:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:260:25: > > 260 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:269:25: > > 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:330:25: > > 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:338:25: > > 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (LOGICAL(4)/INTEGER(4)). > amr_restrict_ec_genorder.F90:310:37: > > > > -- > *Dr. D. P. S. L. Kameswari* > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe:https://urldefense.us/v3/__https://lists.mpich.org/mailman/list… > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://urldefense.us/v3/__https://lists.mpich.org/mailman/listinfo/discuss… >

1 0

Re: [mpich-discuss] Error in MPI_IRECV
by Gregor Corbin 17 Oct '25

17 Oct '25

Hi, let me guess: this code uses `include mpif.h` and is compiled with gfortran. If so, try to add `-fallow-argument-mismatch' to your compiler flags. Explanation: With the include file, there are no explicit interfaces and the compiler generates an implicit interface from the call to `MPI_IRECV`. Having two calls with different argument types is an error since some gcc version (10 IIRC). Cheers, Gregor Corbin On 17.10.25 13:30, phani sri via discuss wrote: > Hi all, I am trying to run FLASH4. 8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. > Thank you in advance. 497 | Call > MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > ZjQcmQRYFpfptBannerEnd > Hi all, I am trying to run FLASH4.8, where I am getting the following > error. Can someone please, suggest to me why this error is coming. > Thank you in advance. > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 633 | Call MPI_IRECV(buffert(1,i),buf_size, & > | 1 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:642:23: > > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:717:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & > | 1 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:725:23: > > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > ...... > 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:260:25: > > 260 | Call MPI_IRECV(buffert(1,i),buf_size, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:269:25: > > 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, > & > | 1 > ...... > 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (LOGICAL(4)/INTEGER(4)). > amr_migrate_tree_data.F90:330:25: > > 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (REAL(8)/INTEGER(4)). > amr_migrate_tree_data.F90:338:25: > > 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, > & > | 1 > ...... > 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, > & > | 2 > Error: Type mismatch between actual argument at (1) and actual > argument at (2) (LOGICAL(4)/INTEGER(4)). > amr_restrict_ec_genorder.F90:310:37: > > > > -- > *Dr. D. P. S. L. Kameswari** > * > > _______________________________________________ > discuss mailing listdiscuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Error in MPI_IRECV
by phani sri 17 Oct '25

17 Oct '25

Hi all, I am trying to run FLASH4.8, where I am getting the following error. Can someone please, suggest to me why this error is coming. Thank you in advance. 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 ...... 633 | Call MPI_IRECV(buffert(1,i),buf_size, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:642:23: 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 ...... 642 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:717:23: 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 ...... 717 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:725:23: 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 ...... 725 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & | 1 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:260:25: 260 | Call MPI_IRECV(buffert(1,i),buf_size, & | 1 ...... 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:269:25: 269 | Call MPI_IRECV(newchildt(i),1,MPI_LOGICAL, & | 1 ...... 497 | Call MPI_IRECV(parentt(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_migrate_tree_data.F90:330:25: 330 | Call MPI_SSEND(buffer(1),buf_size,amr_mpi_real, & | 1 ...... 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/INTEGER(4)). amr_migrate_tree_data.F90:338:25: 338 | Call MPI_SSEND(newchild(i),1,MPI_LOGICAL, & | 1 ...... 513 | Call MPI_SSEND (new_loc(1,i),2,MPI_INTEGER, & | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (LOGICAL(4)/INTEGER(4)). amr_restrict_ec_genorder.F90:310:37: -- *Dr. D. P. S. L. Kameswari*

1 0

Recommended configure options for MPICH 4.3.x with Valgrind or address-sanitizer
by Eric Chamberland 02 Oct '25

02 Oct '25

Hi, I have been building MPICH with the following configure options for a long time, mainly to keep my code “Valgrind-clean”: === ./configure \ --enable-g=dbg,meminit \ --with-device=ch3:sock \ --enable-romio === This setup worked reasonably well in the past, but recently I’ve been seeing occasional errors with address-sanitizer or valgrind (with 4.3.0 on a single node) such as: === Fatal error in internal_Allreduce_c: Unknown error class, error stack: internal_Allreduce_c(347)...................: MPI_Allreduce_c(sendbuf=0x7ffdeb0b8e90, recvbuf=0x7ffdeb0b8e98, count=1, dtype=0x4c00083a, MPI_SUM, comm=0x84000003) failed MPIR_Allreduce_impl(4826)...................: MPIR_Allreduce_allcomm_auto(4732)...........: MPIR_Allreduce_intra_recursive_doubling(115): MPIC_Sendrecv(266)..........................: MPIC_Wait(90)...............................: MPIR_Wait(751)..............................: MPIR_Wait_state(708)........................: MPIDI_CH3i_Progress_wait(187)...............: an error occurred while handling an event returned by MPIDI_CH3I_Sock_Wait() MPIDI_CH3I_Progress_handle_sock_event(385)..: MPIDI_CH3I_Socki_handle_read(3647)..........: connection failure (set=0,sock=1,errno=104:Connection reset by peer) === Is CH3 considered legacy? I would like to also ask: 1. What are the recommended configure options in 2025 for building MPICH in a way that works well with Valgrind? 2. Is it preferable now to move to CH4 (e.g. ch4:ofi or ch4:shm) when debugging with Valgrind? 3. Are there any other options (besides --enable-g=dbg,meminit) that you would suggest for catching memory errors while keeping Valgrind reports as clean as possible? 4. Is https://urldefense.us/v3/__https://github.com/pmodels/mpich/blob/main/doc/w… <https://urldefense.com/v3/__https:/github.com/pmodels/mpich/blob/main/doc/w… > up-to-date? Any guidance on the “best practice” configuration for this use case would be greatly appreciated. PETSc guys have some options about debug (https://urldefense.us/v3/__https://gitlab.com/petsc/petsc/-/blob/main/confi… <https://urldefense.com/v3/__https:/gitlab.com/petsc/petsc/-/blob/main/confi… >) but still uses CH3 by default. However Satish uses the configuration described above, at least for valgrind CI. Thanks a lot, Eric -- Eric Chamberland, ing., M. Ing Professionnel de recherche GIREF/Université Laval On 2025-10-02 08:13, Balay, Satish wrote: > We currently use: > > balay@petsc-gpu-02:~$ > /nfs/gce/projects/petsc/soft/u22.04/mpich-4.3.0-p2-ucx/bin/mpichversion > MPICH Version: 4.3.0 > MPICH Release date: Mon Feb 3 09:09:47 AM CST 2025 > MPICH ABI: 17:0:5 > MPICH Device: ch4:ucx > MPICH configure: > --prefix=/nfs/gce/projects/petsc/soft/u22.04/mpich-4.3.0-p2-ucx > --enable-shared --with-device=ch4:ucx --with-pm=hydra --enable-fast=no > --enable-error-messages=all --enable-g=meminit --disable-java > --without-hwloc --disable-opencl --without-cuda --without-hip > MPICH CC: gcc -O0 > MPICH CXX: g++ -O0 > MPICH F77: gfortran -O0 > MPICH FC: gfortran -O0 > MPICH features: threadcomm > > With: > > #MPICH OFI/UCX/valgrind > export FI_PROVIDER=^psm3 > export UCX_SYSV_HUGETLB_MODE=n > export UCX_LOG_LEVEL=error > > Satish > ------------------------------------------------------------------------

1 0