[Bug fortran/41758] [Cleanup] Don't resolve expr in gfc_match_allocate

2009-10-23 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2009-10-23 11:05 --- Fixed with r153494. Closing. -- janus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/41758] [Cleanup] Don't resolve expr in gfc_match_allocate

2009-10-23 Thread janus at gcc dot gnu dot org
--- Comment #3 from janus at gcc dot gnu dot org 2009-10-23 11:01 --- Subject: Bug 41758 Author: janus Date: Fri Oct 23 11:01:38 2009 New Revision: 153494 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=153494 Log: 2009-10-23 Janus Weil PR fortran/41758 * matc

[Bug fortran/41758] [Cleanup] Don't resolve expr in gfc_match_allocate

2009-10-23 Thread janus at gcc dot gnu dot org
-- 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

[Bug fortran/41758] [Cleanup] Don't resolve expr in gfc_match_allocate

2009-10-19 Thread kargl at gcc dot gnu dot org
--- Comment #2 from kargl at gcc dot gnu dot org 2009-10-19 22:29 --- Note, simply commenting out gfc_resolve_expr() leads to regressions in allocate_alloc_opt_4.f90 and allocate_alloc_opt_6.f90. The reduce testcase from *_4.f90 is ! { dg-do compile } program a implicit none integ

[Bug fortran/41758] [Cleanup] Don't resolve expr in gfc_match_allocate

2009-10-19 Thread kargl at gcc dot gnu dot org
--- Comment #1 from kargl at gcc dot gnu dot org 2009-10-19 22:06 --- (In reply to comment #0) > In gfc_match_allocate one finds a call to gfc_resolve_expr, which resolves the > optional SOURCE expression. > > By definition, resolving should be done at resolution stage, and not already