--- Comment #9 from janus at gcc dot gnu dot org 2010-06-12 04:02 ---
Subject: Bug 44430
Author: janus
Date: Sat Jun 12 04:02:27 2010
New Revision: 160645
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=160645
Log:
2010-06-12 Janus Weil ja...@gcc.gnu.org
PR
--- Comment #10 from janus at gcc dot gnu dot org 2010-06-12 04:03 ---
Fixed on trunk and 4.5. Closing.
--
janus at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #8 from janus at gcc dot gnu dot org 2010-06-09 18:38 ---
Subject: Bug 44430
Author: janus
Date: Wed Jun 9 18:38:11 2010
New Revision: 160504
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=160504
Log:
2010-06-09 Janus Weil ja...@gcc.gnu.org
PR
--
tkoenig at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Known to
--- Comment #2 from tkoenig at gcc dot gnu dot org 2010-06-06 20:15 ---
This was between rev. 149577 (works) and rev. 149607 (does not work).
Still narrowing it down a bit.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44430
--- Comment #3 from dominiq at lps dot ens dot fr 2010-06-06 20:39 ---
This was between rev. 149577 (works) and rev. 149607 (does not work).
The only candidate I see is 149586.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44430
--- Comment #4 from tkoenig at gcc dot gnu dot org 2010-06-06 20:52 ---
I agree. Rev. 149586 is:
2009-07-13 Janus Weil ja...@gcc.gnu.org
PR fortran/40646
* module.c (mio_symbol): If the symbol has formal arguments,
the formal namespace will be present.
*
--- Comment #5 from janus at gcc dot gnu dot org 2010-06-06 21:31 ---
I'm afraid you're right. r149586 indeed seems to be the culprit. The bug goes
away when reverting a part of that commit, more precisely this one:
Index: gcc/fortran/resolve.c
--- Comment #6 from janus at gcc dot gnu dot org 2010-06-06 21:45 ---
A simple way to fix this:
Index: gcc/fortran/dump-parse-tree.c
===
--- gcc/fortran/dump-parse-tree.c (revision 160347)
+++
--
janus at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |janus at gcc dot gnu dot org
|dot org
--- Comment #7 from janus at gcc dot gnu dot org 2010-06-06 21:50 ---
(In reply to comment #5)
The bug goes away when reverting a part of that commit
Of course simply reverting that part causes a couple of regressions, e.g.
proc_ptr_1,10,22 and others.
--
11 matches
Mail list logo