public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/16404] should reject invalid code with -pedantic -std=f95 ? (x8)
Date: Fri, 16 Jul 2004 00:39:00 -0000 [thread overview]
Message-ID: <20040716003945.17765.qmail@sourceware.org> (raw)
In-Reply-To: <20040707093303.16404.jv244@cam.ac.uk>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-07-16 00:39 -------
Subject: Bug 16404
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: tobi@gcc.gnu.org 2004-07-16 00:39:40
Modified files:
gcc/fortran : ChangeLog io.c match.c parse.c parse.h
Log message:
PR fortran/16404
(parts ported from g95)
* parse.h (gfc_state_data): New field do_variable.
(gfc_check_do_variable): Add prototype.
* parse.c (push_state): Initialize field 'do_variable'.
(gfc_check_do_variable): New function.
(parse_do_block): Remember do iterator variable.
(parse_file): Initialize field 'do_variable'.
* match.c (gfc_match_assignment, gfc_match_do,
gfc_match_allocate, gfc_match_nullify, gfc_match_deallocate):
Add previously missing checks.
(gfc_match_return): Reformat error message.
* io.c (match_out_tag): New function.
(match_open_element, match_close_element,
match_file_element, match_dt_element): Call match_out_tag
instead of match_vtag where appropriate.
(match_io_iterator, match_io_element): Add missing check.
(match_io): Reformat error message.
(match_inquire_element): Call match_out_tag where appropriate.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.130&r2=1.131
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/io.c.diff?cvsroot=gcc&r1=1.12&r2=1.13
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/match.c.diff?cvsroot=gcc&r1=1.18&r2=1.19
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/parse.c.diff?cvsroot=gcc&r1=1.13&r2=1.14
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/parse.h.diff?cvsroot=gcc&r1=1.3&r2=1.4
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16404
next prev parent reply other threads:[~2004-07-16 0:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 9:33 [Bug fortran/16404] New: [gfortran] " jv244 at cam dot ac dot uk
2004-07-11 12:43 ` [Bug fortran/16404] " tobi at gcc dot gnu dot org
2004-07-11 13:35 ` [Bug fortran/16404] " cvs-commit at gcc dot gnu dot org
2004-07-11 13:49 ` tobi at gcc dot gnu dot org
2004-07-11 13:54 ` tobi at gcc dot gnu dot org
2004-07-11 14:16 ` cvs-commit at gcc dot gnu dot org
2004-07-11 14:17 ` tobi at gcc dot gnu dot org
2004-07-11 23:22 ` giovannibajo at libero dot it
2004-07-11 23:40 ` tobi at gcc dot gnu dot org
2004-07-13 21:48 ` tobi at gcc dot gnu dot org
2004-07-14 7:53 ` jv244 at cam dot ac dot uk
2004-07-16 0:39 ` cvs-commit at gcc dot gnu dot org [this message]
2004-07-16 0:41 ` tobi at gcc dot gnu dot org
2004-07-16 0:57 ` cvs-commit at gcc dot gnu dot org
2004-09-01 14:36 ` tobi at gcc dot gnu dot org
2004-09-01 21:07 ` cvs-commit at gcc dot gnu dot org
2005-03-13 0:05 ` tobi at gcc dot gnu dot org
2005-06-18 21:52 ` fxcoudert at gcc dot gnu dot org
2005-09-07 16:09 ` pault at gcc dot gnu dot org
2005-09-26 19:28 ` pault at gcc dot gnu dot org
2005-10-01 7:40 ` cvs-commit at gcc dot gnu dot org
2005-10-01 15:58 ` pinskia at gcc dot gnu dot org
[not found] <bug-16404-6642@http.gcc.gnu.org/bugzilla/>
2005-10-12 5:43 ` cvs-commit 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=20040716003945.17765.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).