This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, Aug 28, 2009 at 11:06:31AM +0100, IainS wrote:I do not see a fortran interface definition for this module; rather the c functions appear to be exported in a specific namespace (__iso_c_binding_).
This is largely historical. IIRC, it has been established that the _gfortran_ prefix should be used by the routines in libgfortran. However, with symbol versioned in libraries, gfortran now needs to retain the __iso_c_binding_ prefix.
if I want to add a subroutine to libgfortran which is
FOO(BAR) LOGICAL, INTENT(OUT) :: BAR
do I need to provide a series of c functions (in libgfortran/ intrinsics/ ) viz:
See the scripts in the m4/ subdirectory. You basically need
to write a foo.m4 script that when processed will generated all of the possible functions for the target. The generated
files are placed into the generated/ directory.
-- Janne Blomqvist
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |