public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51268] [Regression] A subroutine can not know anymore its own interface
Date: Tue, 22 Nov 2011 16:42:00 -0000	[thread overview]
Message-ID: <bug-51268-4-dWyNs5tbLW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51268-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-22 16:09:19 UTC ---
Well, that one now gets a diagnostic and didn't get one before is a change, but
the question is whether it is a progression or a regression.

NAG prints:
  Error: line 15: USE MYINTERFACES in program-unit MYSUB imports symbol MYSUB

g95 prints:
  Module 'myinterfaces' at (1) redefines the current program unit 'mysub'

pathf95 prints:
  "MYSUB" is the name of this program unit, therefore it must not be use 
  associated from module "MYINTERFACES".

openf95 prints:
  "MYSUB" is the name of this program unit, therefore it must not be use 
  associated from module "MYINTERFACES".

crayftn prints:
  "MYSUB" is the name of this program unit, therefore it must not be use 
  associated from module "MYINTERFACES".

While ifort prints (only with -stand f95/f03):
  warning #7925: An interface-block in a subprogram shall not contain an
  interface-body for a procedure defined by that subprogram.   [MYSUB]

And "pgf90 -Minfo=all" and "sunf95 -w0" simply silently accept the program.


I think the program is indeed invalid - but if needed, I can check the
standard. One could consider allowing it with a warning (as ifort does), but I
am not sure one should.


  reply	other threads:[~2011-11-22 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 13:32 [Bug fortran/51268] New: " bardeau at iram dot fr
2011-11-22 16:42 ` burnus at gcc dot gnu.org [this message]
2011-11-23  9:34 ` [Bug fortran/51268] " bardeau at iram dot fr
2011-11-23 10:54 ` burnus at gcc dot gnu.org
2011-11-23 14:20 ` bardeau at iram dot fr
2011-11-23 17:17 ` burnus at gcc dot gnu.org
2011-11-24 14:14 ` bardeau at iram dot fr
2011-11-24 14:45 ` burnus at gcc dot gnu.org
2011-11-24 16:35 ` bardeau at iram dot fr
2011-11-29 14:29 ` burnus at gcc dot gnu.org
2011-11-29 14:48 ` bardeau at iram dot fr
2011-11-29 15:24 ` burnus at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-51268-4-dWyNs5tbLW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).