public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bdavis9659 at comcast dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/14066] New: [gfortran] Infinite DO loops not recognized. Date: Sat, 07 Feb 2004 19:55:00 -0000 [thread overview] Message-ID: <20040207195550.14066.bdavis9659@comcast.net> (raw) Do loops like these: DO ... ENDDO and DO 100 ... 100 CONTINUE are probably not standard F77, but are used in existing code. both of these work with g77. Below is a (non) compilable example. $ cat dl.f I = 0 DO 10 IF (I.EQ.20) EXIT I = I + 1 10 CONTINUE PRINT*,'I is ',I END $ /usr/local/bin/gfortran -static dl.f In file dl.f:2 DO 10 1 Error: Unclassifiable statement at (1) In file dl.f:3 IF (I.EQ.20) EXIT 1 Error: EXIT statement at (1) is not within a loop $ g77 -ff77 dl.f $ ./a.out I is 20 $ /usr/local/bin/gfortran --version GNU Fortran 95 (GCC 3.5-tree-ssa 20040207 (merged 20040126)) Copyright (C) 2003 Free Software Foundation, Inc. -- Summary: [gfortran] Infinite DO loops not recognized. Product: gcc Version: tree-ssa Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bdavis9659 at comcast dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14066
next reply other threads:[~2004-02-07 19:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-07 19:55 bdavis9659 at comcast dot net [this message] 2004-02-07 22:13 ` [Bug fortran/14066] " pinskia at gcc dot gnu dot org 2004-04-22 13:17 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-04-22 13:21 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-01 15:19 ` bdavis at gcc dot gnu dot org 2004-05-08 16:14 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2004-05-08 17:28 ` pinskia at gcc dot gnu dot org 2004-05-14 18:38 ` cvs-commit at gcc dot gnu dot org 2004-05-14 18:47 ` tobi 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=20040207195550.14066.bdavis9659@comcast.net \ --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).