--- Comment #9 from jv244 at cam dot ac dot uk 2009-08-03 10:05 ---
the testcases pass with current trunk. I'll close this as fixed.
--
jv244 at cam dot ac dot uk changed:
What|Removed |Added
--- Comment #8 from dfranke at gcc dot gnu dot org 2009-05-04 18:08 ---
Paul, your patch fixes all issues I came across when compiling my largish set
of fortran sources with -fwhole-file. So, now I "just" need to sort out all the
warnings that came up *cough* ;)
Many thanks!
--
dfra
--- Comment #7 from pault at gcc dot gnu dot org 2009-05-04 10:32 ---
I guess that I should take it :-)
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #6 from pault at gcc dot gnu dot org 2009-05-04 10:31 ---
> For some reason that I do not see right now, cs_base in resolve.c is not being
> pushed or popped correctly.
Ah yes! resolve_codes nulls out cs_base. The problem is fixed by storing
cs_base before calling gfc_res
--- Comment #5 from pault at gcc dot gnu dot org 2009-05-04 10:19 ---
(In reply to comment #2)
> It may be worth noting that there are no warnings in the application about
> labels not being in the same block as the corresponding GOTO if compiled
> without -fwhole-file, but if compiled w
--- Comment #4 from dominiq at lps dot ens dot fr 2009-04-25 17:20 ---
This may also be related to some failures I have seen with the polyhedron
tests, see:
http://gcc.gnu.org/ml/fortran/2009-04/msg00031.html
I particular for
[ibook-dhum] lin/test% gfc -O1 -fwhole-file gas_dyn.f90
gas
--- Comment #3 from dfranke at gcc dot gnu dot org 2009-04-25 17:16 ---
Here's a testcase (doesn't "work" without the extra subroutine):
$> cat goto.for
i = 1
DO
CALL inc(i)
IF (i == 5) GOTO 100
END DO
100 PRINT *, "done"
END
SUBROUTINE
--- Comment #2 from dfranke at gcc dot gnu dot org 2009-04-25 17:02 ---
It may be worth noting that there are no warnings in the application about
labels not being in the same block as the corresponding GOTO if compiled
without -fwhole-file, but if compiled with -fwhole-file some of thes
--- Comment #1 from dominiq at lps dot ens dot fr 2009-04-25 14:10 ---
Confirmed. You don't need the infinite loop to get the bus error, the following
block triggers it also:
456 CONTINUE
go to 500
GO TO 456
500 continue
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?i
