This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libgfortran generated and long double calls
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Jack Howarth <howarth at bromo dot msbb dot uc dot edu>
- Cc: fortran at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Sat, 26 May 2007 23:16:34 -0700
- Subject: Re: libgfortran generated and long double calls
- References: <20070527055053.GA19342@bromo.msbb.uc.edu>
On Sun, May 27, 2007 at 01:50:53AM -0400, Jack Howarth wrote:
> A quick stab at changing...
>
> specific__exp_r16 = exp (parm)
>
> to
>
> specific__exp_r16 = expl (parm)
>
> ...in gcc/libgfortran/generated/_exp_r16.F90
> produced the followimg compilation error on
> Darwin PPC...
>
> ../../../gcc-4.2-20070526/libgfortran/generated/_exp_r16.F90:47.23:
>
> specific__exp_r16 = expl (parm)
> 1
> Error: Function reference to 'expl' at (1) is to a non-PURE procedure within a PURE procedure
Well, that was a stupid thing to do. _exp_r16.F90 is compiled by
a Fortran compiler and expl() is not an intrinsic function in Fortran.
--
Steve