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]

Re: fortran .mod files

From: Ed Hill <ed at eh3 dot com>
To: fortran at gcc dot gnu dot org
Date: Tue, 23 Oct 2007 13:45:02 -0400
Subject: Re: fortran .mod files
References: <20071020222443.GA23353@free.fr> <1192976322.22958.4.camel@localhost.localdomain> <20071022102400.65c5c380@localhost.localdomain> <20071022144109.GA39919@troutmask.apl.washington.edu> <19c433eb0710220800w5a670f7evf9ef33e736ffd267@mail.gmail.com> <20071022150502.GA40256@troutmask.apl.washington.edu> <19c433eb0710220823q1638cedbye9eaea0bce24c9b8@mail.gmail.com>

Hi folks,

I have another (hopefully easy!) question about gfortran *.mod files.  I
understand that they are compiler and target dependant.  My question
is: how compiler dependent?  Do the GCC ABI compatibility rules extend
to *.mod files?  I've searched a bit with Google and am not having any
luck finding a reference.

For instance, is it safe to assume that all *.mod files produced with,
say, gfortran from GCC 4.2.1 will (assuming in all cases an identical
set of compiler flags) be compatible with gfortran as shipped in GCC
4.2.2?

Thank you for your time!

Ed

-- 
Edward H. Hill III, PhD  |  ed@eh3.com  |  http://eh3.com/

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: fortran .mod files
  - From: FX Coudert

References:
- Re: [Fedora-packaging] fortran .mod files
  - From: Ed Hill
- Re: [Fedora-packaging] fortran .mod files
  - From: Steve Kargl
- Re: [Fedora-packaging] fortran .mod files
  - From: François-Xavier Coudert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]