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/36325] specific or generic INTERFACE implies the EXTERNAL attribute
Date: Wed, 28 May 2008 21:29:00 -0000 [thread overview]
Message-ID: <20080528212842.27609.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36325-14773@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from janus at gcc dot gnu dot org 2008-05-28 21:28 -------
Subject: Bug 36325
Author: janus
Date: Wed May 28 21:27:56 2008
New Revision: 136130
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136130
Log:
2008-05-28 Janus Weil <janus@gcc.gnu.org>
PR fortran/36325
PR fortran/35830
* interface.c (gfc_procedure_use): Enable argument checking for
external procedures with explicit interface.
* symbol.c (check_conflict): Fix conflict checking for externals.
(copy_formal_args): Fix handling of arrays.
* resolve.c (resolve_specific_f0, resolve_specific_s0): Fix handling
of intrinsics.
* parse.c (parse_interface): Non-abstract INTERFACE statement implies
EXTERNAL attribute.
2008-05-28 Janus Weil <janus@gcc.gnu.org>
PR fortran/36325
PR fortran/35830
* gfortran.dg/interface_23.f90: New.
* gfortran.dg/gomp/reduction3.f90: Fixed invalid code.
* gfortran.dg/proc_decl_12.f90: New:
* gfortran.dg/external_procedures_1.f90: Fixed error message.
Added:
trunk/gcc/testsuite/gfortran.dg/interface_23.f90
trunk/gcc/testsuite/gfortran.dg/proc_decl_12.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/interface.c
trunk/gcc/fortran/parse.c
trunk/gcc/fortran/resolve.c
trunk/gcc/fortran/symbol.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/external_procedures_1.f90
trunk/gcc/testsuite/gfortran.dg/gomp/reduction3.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36325
next prev parent reply other threads:[~2008-05-28 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 13:36 [Bug fortran/36325] New: " jaydub66 at gmail dot com
2008-05-25 14:03 ` [Bug fortran/36325] " jaydub66 at gmail dot com
2008-05-25 14:46 ` jaydub66 at gmail dot com
2008-05-25 15:37 ` burnus at gcc dot gnu dot org
2008-05-25 16:37 ` janus at gcc dot gnu dot org
2008-05-25 17:12 ` burnus at gcc dot gnu dot org
2008-05-25 19:09 ` janus at gcc dot gnu dot org
2008-05-25 19:59 ` burnus at gcc dot gnu dot org
2008-05-25 22:33 ` janus at gcc dot gnu dot org
2008-05-26 16:50 ` burnus at gcc dot gnu dot org
2008-05-26 18:44 ` janus at gcc dot gnu dot org
2008-05-26 20:34 ` burnus at gcc dot gnu dot org
2008-05-28 21:29 ` janus at gcc dot gnu dot org [this message]
2008-05-28 21:38 ` janus 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=20080528212842.27609.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).