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/30873] [4.1 and 4.2 only] ENTRY without explict RESULT does not work for recursive functions
Date: Thu, 08 Mar 2007 21:06:00 -0000 [thread overview]
Message-ID: <20070308210648.13319.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30873-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from burnus at gcc dot gnu dot org 2007-03-08 21:06 -------
Subject: Bug 30873
Author: burnus
Date: Thu Mar 8 21:06:37 2007
New Revision: 122711
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122711
Log:
2007-03-08 Paul Thomas <pault@gcc.gnu.org>
Tobias Burnus <burnus@net-b.de>
PR fortran/30873
* decl.c (gfc_match_entry): Remove erroneous entry result check.
2007-03-08 Paul Thomas <pault@gcc.gnu.org>
Tobias Burnus <burnus@net-b.de>
PR fortran/30873
* gfortran.dg/entry_9.f90: New test.
Added:
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/entry_9.f90
Modified:
branches/gcc-4_2-branch/gcc/fortran/ChangeLog
branches/gcc-4_2-branch/gcc/fortran/decl.c
branches/gcc-4_2-branch/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30873
next prev parent reply other threads:[~2007-03-08 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 7:51 [Bug fortran/30873] New: incorrect error message for valid code jv244 at cam dot ac dot uk
2007-02-20 16:24 ` [Bug fortran/30873] ENTRY without explict RESULT does not work for recursive functions burnus at gcc dot gnu dot org
2007-02-21 11:03 ` pault at gcc dot gnu dot org
2007-02-21 13:53 ` burnus at gcc dot gnu dot org
2007-03-02 23:03 ` burnus at gcc dot gnu dot org
2007-03-02 23:07 ` [Bug fortran/30873] [4.1 and 4.2 only] " burnus at gcc dot gnu dot org
2007-03-03 3:01 ` patchapp at dberlin dot org
2007-03-08 21:06 ` burnus at gcc dot gnu dot org [this message]
2007-03-08 21:07 ` [Bug fortran/30873] [4.1 " burnus 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=20070308210648.13319.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).