This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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]

[fortran, patch] Audit and patch of F95 and F2003 "non-default kind specifiers" warnings

From: FX <fxcoudert at gmail dot com>
To: gfortran <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Cc: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>, Dominique Dhumieres <dominiq at lps dot ens dot fr>
Date: Fri, 6 Jun 2014 21:38:06 +0200
Subject: [fortran, patch] Audit and patch of F95 and F2003 "non-default kind specifiers" warnings
Authentication-results: sourceware.org; auth=none
References: <20140606164924 dot D63DB105 at mailhost dot lps dot ens dot fr>

> It seems that some of these extensions are not caught by -std=f95

I’ve now audited the I/O specifiers for such warnings too. A warning existed only for EXIST, which was introduced way back by Steve:

> 2010-07-05  Steven G. Kargl  <kargl@gcc.gnu.org>
> 
>         PR fortran/44797
>         * fortran/io.c (resolve_tag): Check EXIST tag is a default logical.

I’ve extended the logical warning to the NAMED, OPENED, and PENDING specifiers. I’ve also audited the integer specifiers, and extended the warning to NUMBER, NEXTREC, and RECL, which were missing.

Bootstrapped and regtested on x86_64-apple-darwin13, OK to commit?

FX

Attachment: io_diagnostics.ChangeLog
Description: Binary data

Attachment: io_diagnostics.diff
Description: Binary data

Follow-Ups:
- Re: [fortran, patch] Audit and patch of F95 and F2003 "non-default kind specifiers" warnings
  - From: Steve Kargl
- Re: [fortran, patch] Audit and patch of F95 and F2003 "non-default kind specifiers" warnings
  - From: FX

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