This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [gfortran,patch] add ISO_FORTRAN_ENV intrinsic module

From: FX Coudert <fxcoudert at gmail dot com>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: Paul Thomas <paulthomas2 at wanadoo dot fr>, GFORTRAN <fortran at gcc dot gnu dot org>, GCC-patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 31 Oct 2006 00:08:00 +0100
Subject: Re: [gfortran,patch] add ISO_FORTRAN_ENV intrinsic module
References: <19c433eb0610260602g64e3c003s6f9a9dcbd1fddc6f@mail.gmail.com> <45466774.6020509@wanadoo.fr> <A8F0D5CC-C2FB-4DE0-A77A-9A606A025CE0@gmail.com> <20061030230300.GA8589@troutmask.apl.washington.edu>

Thanks for the details. I was wondering why your -fintrinsic-module option required a user to specify a path. I now see that the module must match its library and the multilib feature means multiple modules.

I'll note that, -fintrinsic-module can be specified by the user, it's mainly used by the specs to tell the compiler where the multilib- specific pre-compiled modules are. I'm not sure if it was clear in my submission mail.

FX

References:
- RFC: patch to add ISO_FORTRAN_ENV intrinsic module
  - From: François-Xavier Coudert
- Re: RFC: patch to add ISO_FORTRAN_ENV intrinsic module
  - From: Paul Thomas
- [gfortran,patch] add ISO_FORTRAN_ENV intrinsic module
  - From: FX Coudert
- Re: [gfortran,patch] add ISO_FORTRAN_ENV intrinsic module
  - From: Steve Kargl

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