[mpich-discuss] MPICH 3.1.1 and MPI_*_c2f

[Junchao Zhang]

p19 of MPI-3.0 says those _c2f / _f2c routines can be implemented in macros.
Also, MPI Standard only defines them in C. Their Fortran versions are a
non-standard extension.

--Junchao Zhang


On Sat, Jun 28, 2014 at 11:43 AM, Balaji, Pavan <balaji at anl.gov> wrote:

> Chris,
>
> Thanks for the report.  What you suggested below seems reasonable.
>
> I was the one who made the change when I was cleaning up the separation of
> symbols into the appropriate libraries.  The intention was that the f2c
> symbols go into libmpifort, while the c2f symbols go into libmpi.  But
> maybe there is a case for f2c symbols to show up in the C library as well
> (if I got an object from a Fortran module and want to convert it to C).
>
> In any case, it sounds like the execution didn’t match the intention.  I
> remember I had some issue with the c2f/f2c symbols, but I don’t remember
> what that was exactly.  Let me go back and see what the reason for that was.
>
> I think the cleanest solution is to put both c2f and f2c in libmpi, since
> libmpifort has a dependency on libmpi anyway.
>
> I’ve created a ticket so you can keep track of the progress on this:
>
> https://trac.mpich.org/projects/mpich/ticket/2122
>
> Thanks,
>
>   — Pavan
>
> On Jun 26, 2014, at 5:00 AM, Chris January <chris.january at allinea.com>
> wrote:
>
> > Hello all,
> >
> > I noticed that MPICH 3.1.1 changed which libraries symbols go in. The
> > MPI_*_c2f functions are no longer available to source files compiled
> > with mpicc and mpicxx (unless you explicitly add -lmpifort).
> >
> > In our opinion the MPI_*_c2f and MPI_* symbols should be available from
> > all compiler drivers (mpicc, mpicxx, mpif77, mpif90, etc.) without the
> > need to explicitly add -lmpifort. Since they are used to convert values
> > between C and Fortran and vice versa it is natural that one would want
> > to use them from both languages.
> >
> > Existing code which assumes, I believe quite reasonably, that MPI_*_c2f,
> > etc. can be used from mpicc with no extra effort fails to compile with
> > MPICH 3.1.1. I think this is a regression which should be fixed.
> >
> > Yours,
> > Chris January - VP Engineering - Allinea Software Ltd.
> >
> >
> > _______________________________________________
> > discuss mailing list     discuss at mpich.org
> > To manage subscription options or unsubscribe:
> > https://lists.mpich.org/mailman/listinfo/discuss
>
> _______________________________________________
> discuss mailing list     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/20140628/f3180a60/attachment.html>