--- Comment #19 from dagurasu15 at hotmail dot com 2007-08-18 19:08 ---
(In reply to comment #18)
> I think this is the same bug. If not let me know and I'll repost it.
> This is a real bummer. I use this to turn off noise from routines I don't
> have
> control
--- Comment #18 from dagurasu15 at hotmail dot com 2007-08-18 19:06 ---
I think this is the same bug. If not let me know and I'll repost it.
This is a real bummer. I use this to turn off noise from routines I don't have
control of (and I mean ALOT of noise). Maybe there
--- Comment #4 from dagurasu15 at hotmail dot com 2007-08-18 17:58 ---
marking as invalid
--
dagurasu15 at hotmail dot com changed:
What|Removed |Added
--- Comment #3 from dagurasu15 at hotmail dot com 2007-08-18 17:55 ---
As it turns out (not surprisingly), you are correct. It never did work, just
the old compiler didn't catch the runtime error. I usually use a left justify
routine on my strings in the end so I never notice
--- Comment #2 from dagurasu15 at hotmail dot com 2007-08-18 17:48 ---
OK, I don't remember these spaces but you may be right. Also, thinking about
it, g77 doesn't detect these types of runtime errors well, maybe it didn't
really work. Let me rerun with some print st
oduct: gcc
Version: 4.1.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dagurasu15 at hotmail dot com
GCC host triplet: P4
http://gcc.gnu.org/bug
