[mpich-discuss] Segfault in MVAPICH 3.0.4 with the Intel 15.0 compilers

[Zhou, Hui]

Hi Difu,

This is mpich-discuss mailing list, not for intel fortran compiler or openmpi (which seem to be implied in the link you provided). Anyway, just saying having the same issue is very ambiguous. Often it turns out every one have their own different issue. Could you detail your issues here?

—
Hui Zhou



On Nov 13, 2018, at 7:24 PM, 孙迪夫 via discuss <discuss at mpich.org<mailto:discuss at mpich.org>> wrote:


Hi,

I'm having problems same with this mentioned in

https://software.intel.com/en-us/forums/intel-fortran-compiler-for-linux-and-mac-os-x/topic/540673#comment-1929491

as noted in the post, the problem is:

"The MVAPICH2 2.0.1 build causes the bodies of a few FRTL routines to be included in the shared libraries (e.g. for_rtl_init in libmpichf90.so.12). The actual code is included, not just references to be resolved later.  That code is out-of-date and so does not run correctly.

The compiler legitimately puts a call to for_rtl_init, etc. into the generated code.  The link step for MVAPICH2 must be resolving that to a static FRTL library which is not the actual up-to-date FRTL static library.

If we are correct, then this is not a Fortran compiler problem, not a Fortran run-time library problem and not an Intel MPI problem.  It is an MVAPICH2 build problem.

--Patrick"

But I cannot find any solution to it in that post, is there any workaround about it?

Thanks in advance.

Difu

_______________________________________________
discuss mailing list     discuss at mpich.org<mailto:discuss at mpich.org>
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20181114/488f8a7b/attachment.html>