public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/20440] END not as first statement on line breaks in fixed form
[not found] <bug-20440-8513@http.gcc.gnu.org/bugzilla/>
@ 2006-05-08 10:46 ` tobi at gcc dot gnu dot org
2006-05-08 10:49 ` tobi at gcc dot gnu dot org
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: tobi at gcc dot gnu dot org @ 2006-05-08 10:46 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from tobi at gcc dot gnu dot org 2006-05-08 10:46 -------
reduced testcase (not valid, but this is another bug):
i = j; end
This bug has nothign to do with parsing of STOP, it needs:
* a statement preceding the end statement, and
* the end statement must follow a semicolon
--
tobi at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|error with fixed form one- |END not as first statement
|liner (gfortran does not |on line breaks in fixed form
|have a sense of humor) |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20440
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/20440] END not as first statement on line breaks in fixed form
[not found] <bug-20440-8513@http.gcc.gnu.org/bugzilla/>
2006-05-08 10:46 ` [Bug fortran/20440] END not as first statement on line breaks in fixed form tobi at gcc dot gnu dot org
@ 2006-05-08 10:49 ` tobi at gcc dot gnu dot org
2006-05-08 13:00 ` tobi at gcc dot gnu dot org
2006-07-08 10:03 ` pault at gcc dot gnu dot org
3 siblings, 0 replies; 4+ messages in thread
From: tobi at gcc dot gnu dot org @ 2006-05-08 10:49 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from tobi at gcc dot gnu dot org 2006-05-08 10:49 -------
woops, of course I decided to make a valid testcase after I wrote that it
wouldn't be valid
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20440
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/20440] END not as first statement on line breaks in fixed form
[not found] <bug-20440-8513@http.gcc.gnu.org/bugzilla/>
2006-05-08 10:46 ` [Bug fortran/20440] END not as first statement on line breaks in fixed form tobi at gcc dot gnu dot org
2006-05-08 10:49 ` tobi at gcc dot gnu dot org
@ 2006-05-08 13:00 ` tobi at gcc dot gnu dot org
2006-07-08 10:03 ` pault at gcc dot gnu dot org
3 siblings, 0 replies; 4+ messages in thread
From: tobi at gcc dot gnu dot org @ 2006-05-08 13:00 UTC (permalink / raw)
To: gcc-bugs
------- Comment #5 from tobi at gcc dot gnu dot org 2006-05-08 12:59 -------
Wow. This is actually a bad bug, but after trying some stuff, I believe that
it only does bad things when the code is non-standard anyway (lines beginning
with ';').
E.g.
schluter@pcl247d:~/src/pr/20440> cat t.f
program a
; i = j ; end
end
schluter@pcl247d:~/src/pr/20440> ~/src/gcc/build/gcc/f951 t.f -fdump-parse-tree
Namespace: A-H: (REAL 4) I-N: (INTEGER 4) O-Z: (REAL 4)
procedure name = MAIN__
symtree: MAIN__ Ambig 0
symbol MAIN__ (UNKNOWN 0)(PROCEDURE UNKNOWN-INTENT PUBLIC UNKNOWN-PROC
SUBROUTINE)
symtree: a Ambig 0
symbol a (UNKNOWN 0)(PROGRAM UNKNOWN-INTENT UNKNOWN-ACCESS
UNKNOWN-PROC)
MAIN__
Execution times (seconds)
final : 0.00 ( 0%) usr 0.00 ( 0%) sys 0.01 (50%) wall
0 kB ( 0%) ggc
TOTAL : 0.01 0.00 0.02
654 kB
Extra diagnostic checks enabled; compiler may run slowly.
Configure with --disable-checking to disable checks.
schluter@pcl247d:~/src/pr/20440>
The complete line following the semicolon is skipped.
OTOH
schluter@pcl247d:~/src/pr/20440> cat t.f
program a
i = j ; end
end
schluter@pcl247d:~/src/pr/20440> ~/src/gcc/build/gcc/f951 t.f
MAIN__ In file t.f:1
program a
1
In file t.f:3
2
Error: Two main PROGRAMs at (1) and (2)
Execution times (seconds)
parser : 0.00 ( 0%) usr 0.00 ( 0%) sys 0.01 (50%) wall
105 kB (16%) ggc
TOTAL : 0.01 0.00 0.02
655 kB
Extra diagnostic checks enabled; compiler may run slowly.
Configure with --disable-checking to disable checks.
schluter@pcl247d:~/src/pr/20440>
yields the correct error
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20440
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/20440] END not as first statement on line breaks in fixed form
[not found] <bug-20440-8513@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2006-05-08 13:00 ` tobi at gcc dot gnu dot org
@ 2006-07-08 10:03 ` pault at gcc dot gnu dot org
3 siblings, 0 replies; 4+ messages in thread
From: pault at gcc dot gnu dot org @ 2006-07-08 10:03 UTC (permalink / raw)
To: gcc-bugs
------- Comment #6 from pault at gcc dot gnu dot org 2006-07-08 10:03 -------
This is entirely fixed on trunk.
Paul
--
pault at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20440
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-07-08 10:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-20440-8513@http.gcc.gnu.org/bugzilla/>
2006-05-08 10:46 ` [Bug fortran/20440] END not as first statement on line breaks in fixed form tobi at gcc dot gnu dot org
2006-05-08 10:49 ` tobi at gcc dot gnu dot org
2006-05-08 13:00 ` tobi at gcc dot gnu dot org
2006-07-08 10:03 ` pault at gcc dot gnu dot org
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).