public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dir at lanl dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/20224] New: gfortran - flags error on strange, but correct f77 program Date: Sun, 27 Feb 2005 06:25:00 -0000 [thread overview] Message-ID: <20050226174515.20224.dir@lanl.gov> (raw) I have a few old programs that do this - it is legal in f77 and actually has a special name that I cannot recall at the moment. Absoft likes and runs it correctly. [dir:~/tests/gfortran] dir% f77 -o jump jump.f FORTRAN 77 Compiler 8.0a, Copyright (c) 1987-2003, Absoft Corp. [dir:~/tests/gfortran] dir% jump hi hi [dir:~/tests/gfortran] dir% gfortran -o jump jump.f In file jump.f:4 10 continue 1 In file jump.f:9 2 Error: Label at (1) is not in the same block as the GOTO statement at (2) [dir:~/tests/gfortran] dir% cat jump.f program main do 20 i=1,2 go to 30 10 continue 20 continue stop 30 continue write(*,*) 'hi' goto 10 end -- Summary: gfortran - flags error on strange, but correct f77 program Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: dir at lanl dot gov CC: gcc-bugs at gcc dot gnu dot org GCC host triplet: powerpc-apple-darwin7.8.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20224
next reply other threads:[~2005-02-26 17:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-27 6:25 dir at lanl dot gov [this message] 2005-02-27 6:53 ` [Bug fortran/20224] " pinskia at gcc dot gnu dot org 2005-02-27 8:49 ` kargl at gcc dot gnu dot org 2005-02-27 13:00 ` kargl at gcc dot gnu dot org 2005-02-27 13:00 ` [Bug fortran/20224] gfortran - flags error on strange, but correct f66 program pinskia at gcc dot gnu dot org 2005-02-28 1:53 ` tobi at gcc dot gnu dot org 2005-02-28 4:11 ` kargl at gcc dot gnu dot org 2005-05-03 7:05 ` tkoenig 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=20050226174515.20224.dir@lanl.gov \ --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).