[Bug fortran/18993] incorrect parsing in fixed-form

2004-12-15 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Severity|critical|normal Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1899

[Bug fortran/18993] incorrect parsing in fixed-form

2004-12-15 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2004-12-15 18:56 --- Fixed. -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug fortran/18993] incorrect parsing in fixed-form

2004-12-15 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-12-15 18:56 --- Subject: Bug 18993 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2004-12-15 18:55:57 Modified files: gcc/fortran: ChangeLog match.c gcc/testsu

[Bug fortran/18993] incorrect parsing in fixed-form

2004-12-15 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2004-12-15 18:03 --- Patch here: http://gcc.gnu.org/ml/fortran/2004-12/msg00161.html After visual inspection of the statement matchers this problem only seems to affect gfc_match_nullify. -- What|Removed

[Bug fortran/18993] incorrect parsing in fixed-form

2004-12-15 Thread tobi at gcc dot gnu dot org
--- Additional Comments From tobi at gcc dot gnu dot org 2004-12-15 17:33 --- This is much worse than it seems. The problem is in statement matching, e.g. we accept this, as if there was a semicolon on the indicated line: subroutine ordern( ) real, pointer :: aux(:,:) C Nul