--- Comment #6 from dfranke at gcc dot gnu dot org 2009-04-15 12:32 ---
Closing, see comment #5.
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #5 from dfranke at gcc dot gnu dot org 2009-04-14 15:18 ---
Closing as WONTFIX.
Workaround: use -fmax-errors=1 to get only one message at a time.
See http://gcc.gnu.org/ml/fortran/2009-04/msg00149.html for discussion.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24404
--
tobi at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|4.1.0 |---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24404
--
tobi at gcc dot gnu dot org changed:
What|Removed |Added
Severity|normal |enhancement
Target Milestone|--- |4.1.0
http
--- Comment #4 from tobi at gcc dot gnu dot org 2005-11-01 20:14 ---
It remains the ordering of the error messages which in this case is hard to
tackle, I'm tempted to say WONTFIX.
--
tobi at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #3 from tobi at gcc dot gnu dot org 2005-11-01 20:05 ---
Subject: Bug 24404
Author: tobi
Date: Tue Nov 1 20:05:54 2005
New Revision: 106346
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106346
Log:
PR fortran/24404
* resolve.c (resolve_symbol): Outp
--- Comment #2 from tobi at gcc dot gnu dot org 2005-11-01 19:53 ---
The ordering of errors is hard to tackle, the bad error description is easily
fixed on the other hand.
--
tobi at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #1 from denney at seas dot upenn dot edu 2005-10-17 02:43
---
Created an attachment (id=10006)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10006&action=view)
test case that generates the errors
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24404
