[Bug fortran/14993] RAN (extension) intrinsic/function not supported

sgk at troutmask dot apl dot washington dot edu gcc-bugzilla@gcc.gnu.org
Tue Aug 31 20:17:00 GMT 2004


------- Additional Comments From sgk at troutmask dot apl dot washington dot edu  2004-08-31 20:17 -------
Subject: Re:  RAN (extension) intrinsic/function not supported

On Tue, Aug 31, 2004 at 07:21:51PM -0000, tobi at gcc dot gnu dot org wrote:
> 
> ------- Additional Comments From tobi at gcc dot gnu dot org  2004-08-31 19:21 -------
> (In reply to comment #11)
> > Andrew, I don't know how to enclose RAN() in an option.  Reading through
> > intrinsic.c, gfortran builds tables of intrinsic function and subroutine
> > names.  Currently, we can't mark a member of a table for inclusion/exclusion
> > by an option.  Although I agree with you on the use of an option, I think
> > this would require a massive rewrite of intrinsic.c.  Frankly, I lack the
> > skill to do such a rewrite before 3.5 is released.
> 
> What we could do is add an option, say -fno-nonstandard-intrinsics, and
> then conditionalize the add_sym calls for all nonstandard intrinsics on
> this flag not being set, i.e.
> if (!gfc_option.only_standard)
>   {
>     add_sym ("fancyintrinsic");
>     add_sym ("fancyintrinsic2");
>   }
> add_sym ("standardintrinsic");
> etc.
> 

Where are you doing this?  AFAIK, the list of intrinsics is constructed
when gfortran is compiled not when you execute gfortran.  At runtime
we need to be able to regenerate the expected list of intrinsics from
the master.  To me, this means we need to tag each specific and generic
intrinsic procedure with a standard.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14993



More information about the Gcc-bugs mailing list