public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/21104] Segmentation fault on correct code
Date: Sat, 23 Apr 2005 16:47:00 -0000	[thread overview]
Message-ID: <20050423164734.21573.qmail@sourceware.org> (raw)
In-Reply-To: <20050419120240.21104.paulthomas2@wanadoo.fr>


------- Additional Comments From pault at gcc dot gnu dot org  2005-04-23 16:47 -------
It is my belief that this is correct code, after all.

An explicit interface is REQUIRED to invoke a procedure with a pointer or 
target dummy argument or a pointer function result. 

In other circumstances it is advised, as good practice.

Here the compiler can resolve the interface because the result has explicit 
shape.  It should therefore be able to deal with it and produce executable 
code.  At very least, it should emit a message demanding an explicit interface 
and give in gracefully.

PS Andrew, for someone who claims not to know fortran, you seem to get into 
some of its murkier corners!  We'll have you writing fortran code yet...

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-04-23 16:47:32
               date|                            |


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


  parent reply	other threads:[~2005-04-23 16:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 12:02 [Bug fortran/21104] New: " paulthomas2 at wanadoo dot fr
2005-04-19 12:21 ` [Bug fortran/21104] " pinskia at gcc dot gnu dot org
2005-04-19 13:32 ` paulthomas2 at wanadoo dot fr
2005-04-19 16:15 ` fxcoudert at gcc dot gnu dot org
2005-04-19 19:23 ` pinskia at gcc dot gnu dot org
2005-04-23 16:47 ` pault at gcc dot gnu dot org [this message]
2005-04-23 16:58 ` pinskia at gcc dot gnu dot org
2005-04-27 16:05 ` paulthomas2 at wanadoo dot fr
2005-07-23  6:31 ` pinskia at gcc dot gnu dot org
2005-09-05 13:20 ` rsandifo at gcc dot gnu dot org
2005-09-09  6:22 ` cvs-commit at gcc dot gnu dot org
2005-09-09  6:24 ` rsandifo at gcc dot gnu dot org
2005-09-09  6:34 ` cvs-commit at gcc dot gnu dot 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=20050423164734.21573.qmail@sourceware.org \
    --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).