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: ran intrinsic bug?

From: Jerry DeLisle <jvdelisle at verizon dot net>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: Fortran List <fortran at gcc dot gnu dot org>
Date: Sat, 26 Feb 2005 15:34:47 -0800
Subject: Re: ran intrinsic bug?
References: <4220DCFA.9040403@verizon.net> <4220EAD0.3030405@verizon.net><20050226213557.GA97954@troutmask.apl.washington.edu><4220F199.1060404@verizon.net><20050226221320.GA98159@troutmask.apl.washington.edu><4220FCE6.4040000@verizon.net><20050226225556.GA98596@troutmask.apl.washington.edu>

Steve Kargl wrote:

Is this what you're expecting?

Yes, I believe so and I am getting his now. The first time I added the external statement to the top of the main program and it did not work, so I moved it to the matgen subroutine and that works fine. Not exactly g77 compatible because of the gfortran intrinsic, but not difficult to fix at the application level.

I am wondering if there should be a way to "hide" non g77 intrinsics so people do not have to edit old codes. It is coincidental that this program just happened to use a name that is used by a gfortran intrinsic. The compiler can not be omniscient :) or can it?

Jerry

Follow-Ups:
- Re: ran intrinsic bug?
  - From: Steve Kargl

References:
- ran intrinsic bug?
  - From: Jerry DeLisle
- Re: ran intrinsic bug?
  - From: Jerry DeLisle
- Re: ran intrinsic bug?
  - From: Steve Kargl
- Re: ran intrinsic bug?
  - From: Jerry DeLisle
- Re: ran intrinsic bug?
  - From: Steve Kargl
- Re: ran intrinsic bug?
  - From: Jerry DeLisle
- Re: ran intrinsic bug?
  - From: Steve Kargl

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