public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33162] INTRINSIC functions as ACTUAL argument
Date: Wed, 31 Oct 2007 14:27:00 -0000 [thread overview]
Message-ID: <20071031142711.22536.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33162-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from jvdelisle at gcc dot gnu dot org 2007-10-31 14:27 -------
Subject: Bug 33162
Author: jvdelisle
Date: Wed Oct 31 14:26:57 2007
New Revision: 129798
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=129798
Log:
2007-10-31 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR fortran/33162
* interface.c (compare_intr_interfaces): New function to check
intrinsic
function arguments against formal arguments. (compare_interfaces): Fix
logic in comparison of function and subroutine attributes.
(compare_parameter): Use new function for intrinsic as argument.
* resolve.c (resolve_actual_arglist): Allow an intrinsic without
function attribute to be checked further. Set function attribute if
intrinsic symbol is found, return FAILURE if not.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/interface.c
trunk/gcc/fortran/resolve.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33162
next prev parent reply other threads:[~2007-10-31 14:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 16:29 [Bug fortran/33162] New: Type checking absent for specific names of INTRINSIC functions burnus at gcc dot gnu dot org
2007-09-05 14:14 ` [Bug fortran/33162] INTRINSIC functions as ACTUAL argument burnus at gcc dot gnu dot org
2007-10-21 0:15 ` jvdelisle at gcc dot gnu dot org
2007-10-21 3:34 ` jvdelisle at gcc dot gnu dot org
2007-10-21 9:30 ` burnus at gcc dot gnu dot org
2007-10-21 10:44 ` burnus at gcc dot gnu dot org
2007-10-21 16:39 ` jvdelisle at gcc dot gnu dot org
2007-10-21 21:32 ` jvdelisle at gcc dot gnu dot org
2007-10-22 6:56 ` burnus at gcc dot gnu dot org
2007-10-23 1:42 ` jvdelisle at gcc dot gnu dot org
2007-10-27 0:54 ` jvdelisle at gcc dot gnu dot org
2007-10-27 0:57 ` jvdelisle at gcc dot gnu dot org
2007-10-27 21:07 ` burnus at gcc dot gnu dot org
2007-10-31 4:00 ` patchapp at dberlin dot org
2007-10-31 14:27 ` jvdelisle at gcc dot gnu dot org [this message]
2007-10-31 14:31 ` jvdelisle at gcc dot gnu dot org
2007-11-02 5:26 ` jvdelisle at gcc dot gnu dot org
2007-11-02 5:41 ` jvdelisle at gcc dot gnu dot org
2007-11-02 5:56 ` jvdelisle at gcc dot gnu dot org
2007-11-02 20:53 ` jaydub66 at gmail dot com
2007-11-03 22:02 ` jvdelisle at gcc dot gnu dot org
2007-11-12 5:56 ` patchapp at dberlin dot org
2007-11-14 0:59 ` jvdelisle at gcc dot gnu dot org
2007-11-14 1:06 ` jvdelisle at gcc dot gnu dot org
2007-11-14 1:17 ` jvdelisle 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=20071031142711.22536.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).