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/39427] F2003: Procedures with same name as types/type constructors
Date: Tue, 18 May 2010 21:52:00 -0000 [thread overview]
Message-ID: <20100518215153.23606.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39427-15301@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from burnus at gcc dot gnu dot org 2010-05-18 21:51 -------
Created an attachment (id=20696)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20696&action=view)
Fifth draft patch - with test case
New approach. The attached patch now also works with twisted modules (cf. test
case in the attachment). However, it needs still some clean up as there are
test suite failures.
Additional tasks: (a) Check whether one can get rid of
gfc_match_structure_constructor. (b) Add check to ensure that the generic name
only contains functions and that the type name does not exist as specific
function name. (c) Do general clean up, bug fixing, and add test cases.
Regarding C489 [F2003] and C496 [F2008], see also:
http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/b3580ffd988330d7
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #20599|0 |1
is obsolete| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39427
next prev parent reply other threads:[~2010-05-18 21:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 23:32 [Bug fortran/39427] New: Error on generic name equivalent to type name in same module damian at rouson dot net
2009-03-11 22:42 ` [Bug fortran/39427] F2003: Procedures with same name as types/type constructors burnus at gcc dot gnu dot org
2009-03-29 7:31 ` fxcoudert at gcc dot gnu dot org
2009-12-03 21:02 ` burnus at gcc dot gnu dot org
2010-01-23 17:25 ` janus at gcc dot gnu dot org
2010-05-04 12:10 ` steven at gcc dot gnu dot org
2010-05-04 14:25 ` damian at rouson dot net
2010-05-04 16:10 ` burnus at gcc dot gnu dot org
2010-05-04 16:13 ` burnus at gcc dot gnu dot org
2010-05-05 18:09 ` burnus at gcc dot gnu dot org
2010-05-05 18:15 ` burnus at gcc dot gnu dot org
2010-05-07 9:16 ` burnus at gcc dot gnu dot org
2010-05-07 9:20 ` burnus at gcc dot gnu dot org
2010-05-07 16:37 ` burnus at gcc dot gnu dot org
2010-05-18 21:52 ` burnus at gcc dot gnu dot org [this message]
2010-05-20 21:14 ` burnus at gcc dot gnu dot org
2010-05-25 19:55 ` burnus at gcc dot gnu dot org
2010-07-30 9:03 ` burnus at gcc dot gnu dot org
2010-07-31 2:30 ` damian at rouson dot net
2010-08-01 7:26 ` burnus at gcc dot gnu dot org
[not found] <bug-39427-4@http.gcc.gnu.org/bugzilla/>
2010-09-28 23:31 ` damian at rouson dot net
2010-09-30 19:17 ` burnus at gcc dot gnu.org
2010-11-03 9:15 ` burnus at gcc dot gnu.org
2010-12-08 13:11 ` burnus at gcc dot gnu.org
2010-12-28 21:50 ` dfranke at gcc dot gnu.org
2011-01-09 22:07 ` janus at gcc dot gnu.org
2011-03-16 11:41 ` janus at gcc dot gnu.org
2011-10-11 16:17 ` burnus at gcc dot gnu.org
2011-11-09 13:56 ` burnus at gcc dot gnu.org
2011-11-16 21:58 ` burnus at gcc dot gnu.org
2011-11-16 22:28 ` burnus at gcc dot gnu.org
2011-11-17 2:29 ` damian at rouson dot net
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=20100518215153.23606.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).