public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/15190] New: [gfortran] incorrect matching of print statement Date: Wed, 28 Apr 2004 13:35:00 -0000 [thread overview] Message-ID: <20040428123838.15190.Tobias.Schlueter@physik.uni-muenchen.de> (raw) The following free-form code compiles without error: INTEGER f PRINTf, 2 END The parser should enforce a space between print and f. -- Summary: [gfortran] incorrect matching of print statement Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Tobias dot Schlueter at physik dot uni-muenchen dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15190
next reply other threads:[~2004-04-28 12:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-28 13:35 Tobias dot Schlueter at physik dot uni-muenchen dot de [this message] 2004-04-28 14:27 ` [Bug fortran/15190] " pinskia at gcc dot gnu dot org 2004-04-30 16:35 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-16 21:42 ` [Bug fortran/15190] [gfortran] incorrect matching tobi at gcc dot gnu dot org 2004-05-27 3:25 ` pinskia at gcc dot gnu dot org 2004-06-25 13:13 ` [Bug fortran/15190] incorrect matching after keywords tobi at gcc dot gnu dot org 2004-06-25 13:35 ` tobi at gcc dot gnu dot org 2004-06-26 11:50 ` tobi at gcc dot gnu dot org 2004-06-26 12:15 ` cvs-commit at gcc dot gnu dot org 2004-07-10 0:36 ` pinskia 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=20040428123838.15190.Tobias.Schlueter@physik.uni-muenchen.de \ --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: linkBe 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).