Thomas, If you can build MPICH with gfortran (which is easy in my opinion), then you can easily do the experiment. Attaching a debugger, within a few steps, you run into gfortran code. Watching the address where the array's start index is stored, you can immediately find the bug. Otherwise, Hui has to separate out the few C/Fortran wrappers and make them MPI independent to make a test code. --Junchao Zhang On Thu, Nov 21, 2019 at 11:17 AM Zhou, Hui <[email protected]<mailto:[email protected]>> wrote: Hi Thomas, Just to follow up. I will try to isolate a reproducing example at some point (unless someone beats me). — Hui Zhou On Nov 15, 2019, at 12:48 PM, Thomas König via discuss <[email protected]<mailto:[email protected]>> wrote: Hi Junchao, Could you check if it is a gcc bug in handling type(*), dimension(..) Unfortunately, I don't know the code that well to be able to do it. If you could put together a simple, self-contained test case showing i there is a problem, you could submit that to gcc's bugzilla (or I could do that for you). I could also check a simplified test case against current gfortran trunk, which will not compile mpich 3.3.1 because it now flags argument mismatches as errors. (And yes, argument mismatches are real errors, which cause wrong code; see for example https://bugs.debian.org/944127 .) _______________________________________________ discuss mailing list [email protected]<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss