public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61069] Gfortran allows functions to be called as subroutines when defined in a separate source file
Date: Tue, 06 May 2014 17:38:00 -0000	[thread overview]
Message-ID: <bug-61069-4-zvPcflAcmK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61069-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, May 06, 2014 at 03:41:13PM +0000, tristanmoody at gmail dot com wrote:
> 
> I concede this point: the standard only specifies that the compiler catch
> nonconforming code within individual program units -- it does not make any
> statement about how to handle when the nonconformance is specifically the
> relationship between program units.  That is why I would agree with a "wontfix"
> resolution.  Note 1.11 of the Fortran 2008 standard states that the compiler's
> documentation should state what additional forms and relationships it allows. 
> I would take that to include instances such as this where nonconforming,
> invalid code is accepted and executable.
> 

The Fortran code conforms to the Fortran standard!  Why do you continue to
claim that it is nonconforming invalid code.  What the linker does to 
the object code after the Fortran processor has created the three object
files is beyond the scope of the Fortran standard.


  parent reply	other threads:[~2014-05-06 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-61069-4@http.gcc.gnu.org/bugzilla/>
2014-05-05 22:33 ` dominiq at lps dot ens.fr
2014-05-05 23:30 ` tristanmoody at gmail dot com
2014-05-06 11:30 ` kargl at gcc dot gnu.org
2014-05-06 17:38 ` sgk at troutmask dot apl.washington.edu [this message]
2014-05-06 17:42 ` pinskia at gcc dot gnu.org
2014-05-06 18:17 ` tristanmoody at gmail dot com
2014-05-06 18:43 ` sgk at troutmask dot apl.washington.edu
2014-05-06 18:53 ` tristanmoody at gmail dot com

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-61069-4-zvPcflAcmK@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).