public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42418] PROCEDURE: Rejects interface which is both specific and generic procedure
Date: Sat, 19 Dec 2009 20:27:00 -0000	[thread overview]
Message-ID: <20091219202741.18087.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42418-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from janus at gcc dot gnu dot org  2009-12-19 20:27 -------
(In reply to comment #1)
> The following program is also rejected, unless the marked line is
> removed/comment out. At a glance, it looks OK - and ifort, NAG f95 and g95
> accept it. The error message is:
> 
> 
>    print *, fun(enisoc, [0.0])
>                 1
> Error: ELEMENTAL non-INTRINSIC procedure 'enisoc' is not allowed as an actual
> argument at (1)

This one I can not confirm. With a clean trunk at r155303 I do not see the
error message on x86_64-unknown-linux-gnu.


-- 


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


  parent reply	other threads:[~2009-12-19 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 22:51 [Bug fortran/42418] New: PROCEDURE: Rejects interfface " burnus at gcc dot gnu dot org
2009-12-17 23:02 ` [Bug fortran/42418] PROCEDURE: Rejects interface " burnus at gcc dot gnu dot org
2009-12-19 20:27 ` janus at gcc dot gnu dot org [this message]
     [not found] <bug-42418-4@http.gcc.gnu.org/bugzilla/>
2011-01-09 19:07 ` janus at gcc dot gnu.org
2011-01-09 22:02 ` janus at gcc dot gnu.org
2012-01-28 23:17 ` dominiq at lps dot ens.fr
2012-07-21  9:52 ` janus at gcc dot gnu.org
2012-07-21 17:10 ` janus at gcc dot gnu.org
2012-07-31 18:33 ` janus at gcc dot gnu.org
2012-07-31 18:39 ` janus 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=20091219202741.18087.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).