--- Comment #5 from fxcoudert at gcc dot gnu dot org 2006-11-16 07:51
---
Closing, since this was already fixed. Please reopen (or open a new report) if
you have another example of such behaviour with an up-to-date compiler.
--
fxcoudert at gcc dot gnu dot org changed:
W
--- Comment #4 from tobias dot burnus at physik dot fu-berlin dot de
2006-11-01 14:01 ---
This has been fixed in the meanwhile.
(Don't forget, gfortran is not that old.)
Possibilities:
- Use a GCC 4.1 branch build (newer than 4.1.1)
- Use a GCC 4.2 branch build
- Use a GCC 4.3 trunk bu
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-10-31 21:48 ---
*** Bug 29678 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-10-31 21:41 ---
The other thing is with debugging option such as -fbounds-check, you can also
use gdb to figure out which one.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29677
--- Comment #1 from kargl at gcc dot gnu dot org 2006-10-31 21:38 ---
Upgrade to the a 4.2 pre-release version of gfortran or
the mainline version. Please report back if you find
a problem.
--
kargl at gcc dot gnu dot org changed:
What|Removed |Ad
