public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40276] Matching GENERIC procedure: Wrong INTENT should give directly an error message
Date: Wed, 27 May 2009 21:40:00 -0000	[thread overview]
Message-ID: <20090527214023.18703.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40276-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from burnus at gcc dot gnu dot org  2009-05-27 21:40 -------
Created an attachment (id=17922)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17922&action=view)
Very initial draft patch

Some patch; now it prints:

    call gen(sub)
             1
Error: Type/rank mismatch in argument 'a' at (1)

Maybe together with the patch which gives better error messages this will
produce something useful. Currently it is better than before, but only
marginally. I think it should state somewhere that the generic procedure
matches a specific one (and only the INTENT goes wrong). I think it should
print somewhere the procedure name of the specific function. With all the
recursion, having a proper error message is not trivial.

I had to remove the intents_check() as it does not do recursive checks. And I
could not easily do a a recursive call as then one has two formal arguments
rather than a formal and an actual arguments.


-- 


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


  reply	other threads:[~2009-05-27 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 18:34 [Bug fortran/40276] New: " burnus at gcc dot gnu dot org
2009-05-27 21:40 ` burnus at gcc dot gnu dot org [this message]
2009-06-15 22:40 ` [Bug fortran/40276] " burnus at gcc dot gnu dot org
2009-12-18 14:37 ` pault at gcc dot gnu dot org
     [not found] <bug-40276-4@http.gcc.gnu.org/bugzilla/>
2013-07-16  6: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=20090527214023.18703.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).