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/29806] Error if CONTAINS is present without SUBPROGRAM
Date: Wed, 15 Nov 2006 10:02:00 -0000 [thread overview]
Message-ID: <20061115100234.13937.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29806-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from burnus at gcc dot gnu dot org 2006-11-15 10:02 -------
Subject: Bug 29806
Author: burnus
Date: Wed Nov 15 10:02:21 2006
New Revision: 118851
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118851
Log:
fortran/
2006-11-15 Tobias Burnus <burnus@net-b.de>
PR fortran/29806
* parse.c (parse_contained): Check for empty contains statement.
testsuite/
2006-11-15 Tobias Burnus <burnus@net-b.de>
PR fortran/29806
* gfortran.dg/contains.f90: New test.
* gfortran.dg/derived_function_interface_1.f90: Add a dg-warning.
Added:
trunk/gcc/testsuite/gfortran.dg/contains.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/parse.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/derived_function_interface_1.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29806
next prev parent reply other threads:[~2006-11-15 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 22:44 [Bug fortran/29806] New: " burnus at gcc dot gnu dot org
2006-11-12 21:02 ` [Bug fortran/29806] " burnus at gcc dot gnu dot org
2006-11-13 7:42 ` erik dot edelmann at iki dot fi
2006-11-13 10:05 ` burnus at gcc dot gnu dot org
2006-11-13 18:55 ` patchapp at dberlin dot org
2006-11-14 7:43 ` burnus at gcc dot gnu dot org
2006-11-15 10:02 ` burnus at gcc dot gnu dot org [this message]
2006-11-15 10:14 ` burnus at gcc dot gnu dot org
2006-12-01 2:03 ` chaoyingfu 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=20061115100234.13937.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).