[Bug fortran/35033] Valid ASSIGNMENT(=) rejected

2008-02-26 Thread burnus at gcc dot gnu dot org
--- Comment #5 from burnus at gcc dot gnu dot org 2008-02-26 22:41 --- FIXED on the trunk (4.4.0). The not-so-helpful error message is now PR 35267. -- burnus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/35033] Valid ASSIGNMENT(=) rejected

2008-02-26 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2008-02-26 22:34 --- Subject: Bug 35033 Author: burnus Date: Tue Feb 26 22:33:35 2008 New Revision: 132689 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=132689 Log: 2008-02-26 Tobias Burnus <[EMAIL PROTECTED]> PR fort

[Bug fortran/35033] Valid ASSIGNMENT(=) rejected

2008-01-30 Thread burnus at gcc dot gnu dot org
--- Comment #3 from burnus at gcc dot gnu dot org 2008-01-30 22:29 --- Created an attachment (id=15059) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15059&action=view) Patch - build & regtested (x86-64-linux) Patch fixes actual problem and includes a test case. Missing is only im

[Bug fortran/35033] Valid ASSIGNMENT(=) rejected

2008-01-30 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2008-01-30 18:25 --- Created an attachment (id=15057) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15057&action=view) Draft Patch First patch: - Better error message - Fix that check But ... The volatile constrain is properly tak

[Bug fortran/35033] Valid ASSIGNMENT(=) rejected

2008-01-30 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2008-01-30 17:22 --- "Error: Assignment operator interface at (1) must not redefine an INTRINSIC type assignment" The error message by itself is correct - but a) The position is very bad it should point to SUBROUTINE and not to END SUBRO