This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/24447] dimag_ undefined error with -std=f95
- From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 20 Oct 2005 01:18:49 -0000
- Subject: [Bug fortran/24447] dimag_ undefined error with -std=f95
- References: <bug-24447-8649@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from sgk at troutmask dot apl dot washington dot edu 2005-10-20 01:18 -------
Subject: Re: dimag_ undefined error with -std=f95
On Thu, Oct 20, 2005 at 01:10:06AM -0000, uttamp at us dot ibm dot com wrote:
>
> Finally I found the f95 standard document (1539-1-1997) and did not
> see dimag() mentioned in there. I was looking at PGI Fortran Reference
> document all this time and there was not comment about dimag() as an
> extension. my apologies for causing all the extra work to cross-verify
> it. I was just too quick to send patch to gcc-patches mailing list.
As far as I'm concerned, this type of bug report isn't too much
of a problem. It shows our user base is trying gfortran and
any attempts to expose bugs are welcomed.
Unfortunately, you've hit an area where there are numerous de facto
intrinsic procedures, which are not specified by the standard, but
everyone uses. The -std=f95 flag will expose their use. I suppose
I should add a big warning to the docs about this behavior with
-std=f95.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24447