This is the mail archive of the
mailing list for the GCC project.
Re: [gfortran] Patch for PR 17590: Tagging intrinsics with standard version
- From: Paul Brook <paul at codesourcery dot com>
- To: fortran at gcc dot gnu dot org
- Cc: Janne Blomqvist <jblomqvi at cc dot hut dot fi>, gcc-patches at gcc dot gnu dot org
- Date: Sun, 3 Oct 2004 15:31:49 +0100
- Subject: Re: [gfortran] Patch for PR 17590: Tagging intrinsics with standard version
- Organization: CodeSourcery
- References: <20040922194430.GA12720@vipunen.hut.fi>
On Wednesday 22 September 2004 20:44, Janne Blomqvist wrote:
> The following patch tags all intrinsic subroutines and functions with
> a standard version, and prints out error or warning messages if an
> intrinsic does not exist in the standard the user has chosen (via the
> -std flag). The intrinsics are flagged as belonging to either F77,
> F95, F2003 or GNU. The available choices for the user has not changed
> e.g. they are default (basically F95 + GNU extensions), f95, f2003 or
> gnu (everything we have).
Wouldn't it be better to ignore the intrinsic if it doesn't belong to the
I would expect --std=f95 to allow the user to define and call user functions
with the same name as (nonstandard) intrinsics. We resolve intrinsics to
special names, so the user would still get link errors if they tried to use
An option to warn/error about nonstandard intrinsics would probably be a good
idea, but I don't think it should be directly tied to --std=.